Malicious PDF — malware analysis report

Static analysis result for SHA-256 b7ef2ab6555299c3…

MALICIOUS

PDF

30.6 KB
MD5: 1c810b9823428a9aea45a3ff9643f569 SHA-1: 02ad370433941c49e4a363f9437d27d441790ed5 SHA-256: b7ef2ab6555299c3287baf70ef3ea16795eae53cb1804ebd3f910cd777b892d2
196 Risk Score

Malware Insights

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

The PDF sample contains high-severity heuristics indicating embedded executable scripts and the use of JavaScript functions like eval() and unescape(), commonly used for obfuscation and payload delivery. The ML classifier strongly flags this as malicious. The presence of an embedded file, 'embedded_file_obj0008.bin', suggests it's a dropper for a secondary stage. The document body content is not indicative of a specific lure.

Machine Learning

  • Nyx PDF Classifier malicious score 1.0000

Heuristics 9

  • XFA form contains risky executable script high CVE related PDF_XFA_SCRIPT
    PDF embeds an XFA form whose script block contains exploit, submission/launch, or shell-execution primitives. Ordinary LiveCycle print/update scripts are left as generic XFA/JS signals unless stronger behavior is present.
  • eval() call high PDF_EVAL
    eval() found — commonly used for obfuscated exploit execution
  • unescape() call high PDF_UNESCAPE
    unescape() found — often used to decode shellcode in PDF JS exploits
  • Embedded script payload in PDF stream medium PDF_EMBEDDED_SCRIPT_PAYLOAD
    PDF stream bytes contain an HTML/XFA <script> tag without accompanying Windows shell-execution primitives — common in accessible XFA forms but worth surfacing for analyst review.
  • 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.
  • 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/xfa-template/2.5/
    • http://www.xfa.org/schema/xfa-data/1.0/

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
embedded_file_obj0008.bin
ec98e8c0abfd5c122dcd59faeeec5a57a46ee0af148a765081470db922861390
pdf-embedded-file PDF EmbeddedFile object 8 at offset 0xC6 30647 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 4 eval/decoder/string-building token(s).