Malicious PDF — malware analysis report

Static analysis result for SHA-256 84a0ce5e2e591e83…

MALICIOUS

PDF

29.8 KB
MD5: 495b8f10c0f67267e7881336f003a5df SHA-1: bd7d659d9d2087fff2ff2dd6d66c8a9a816fd8db SHA-256: 84a0ce5e2e591e830b34457c6d5f35d5314a99073df8543b0f8deded206eb0b5
82 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell T1204.002 Malicious File

The PDF file contains embedded JavaScript and a RichMedia (Flash) object, indicating an attempt to exploit vulnerabilities. The presence of 'javascript_obj0006_000.js' suggests that JavaScript is used to initiate malicious activity. The embedded JavaScript is likely responsible for downloading and executing a second-stage payload, as indicated by the 'PDF_JAVASCRIPT' and 'PDF_JS' heuristic firings. The confidence is moderate due to the lack of specific script content for detailed analysis.

Heuristics 8

  • RichMedia (Flash) high PDF_RICHMEDIA
    PDF contains /RichMedia (Adobe Flash) which is a historic exploit vector
  • JavaScript action low PDF_JAVASCRIPT
    PDF contains a /JavaScript action. Generic JavaScript is common in benign forms; specific dangerous APIs are scored by separate rules.
  • Embedded JS stream low PDF_JS
    PDF references a /JS stream. Generic JavaScript is common in benign forms; specific dangerous APIs are scored by separate rules.
  • Embedded file low PDF_EMBEDDED
    PDF embeds a file attachment — could carry an executable or another weaponised document as a nested payload
  • XFA form low PDF_XFA
    PDF uses XML Forms Architecture — can contain script logic
  • String.fromCharCode low PDF_FROMCHARCODE
    String.fromCharCode found — used to construct payload strings dynamically. Common in benign JavaScript libraries for codepoint manipulation, so this alone is informational; weaponised use is also caught by the dedicated fromCharCode-stage and exploit-shape rules. (matched inside decoded stream)
  • Suspicious extracted artifact info EXTRACTED_FILE_STATIC_TRIAGE
    One or more files extracted from inside this sample matched static suspicious-content checks such as script obfuscation, encoded payload blobs, packed data, or execution/download terms.
  • Embedded URL info EMBEDDED_URL
    One or more URLs were extracted from the document. The URL itself is not a detection — see the per-URL labels for which channel (macro, JS, link annotation, document body, ...) reached each URL.
    URL http://ns.adobe.com/xdp/
    • http://www.xfa.org/schema/xci/2.6/
    • http://www.xfa.org/schema/xfa-template/2.6/

Extracted artifacts 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
embedded_file_obj0016.bin
4d4d42d908c48737d0cbe1f33c14f197803950e6ff47f9c0f13e1d51a231494d		 pdf-embedded-file PDF EmbeddedFile object 16 at offset 0x8CA 53991 bytes
javascript_obj0006_000.js
84c06f4fe2d0edaae2970c7ae11f7a839854ea2c1f2c7b924d59411d10cd4c02		 pdf-javascript-stream PDF /JS object 6 at offset 0x106 11498 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 239 eval/decoder/string-building token(s).

Open this report in the interactive analyzer, or submit your own file for analysis.