Malicious PDF — malware analysis report

Static analysis result for SHA-256 7c60d0e1cd1b2dbc…

MALICIOUS

PDF

9.3 KB
MD5: 212937868b1ea2440df2674bd26c6c19 SHA-1: 876f66f69a1a3c1a0196cd4e4e0a63f7029dcba6 SHA-256: 7c60d0e1cd1b2dbc813b20287f88fa2016daca47e5101ad7346513345638f26e
158 Risk Score

Malware Insights

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

The PDF contains XFA forms and uses JavaScript, indicated by PDF_XFA_SCRIPT and PDF_EMBEDDED_SCRIPT_PAYLOAD heuristics. The ML classifier strongly flags this PDF as malicious. The deobfuscated.js file and embedded_file_obj0041.bin are suspicious artifacts extracted from the PDF, suggesting it's designed to deliver a secondary payload. The eval() call and String.fromCharCode usage point to script execution.

Machine Learning

  • Nyx PDF Classifier malicious score 1.0000

Heuristics 7

  • 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 (matched inside decoded stream)
  • 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. (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.

Extracted artifacts 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
embedded_file_obj0041.bin
be8df18be8d9afdec2cdf78f57f09b64123600376e32ffca062ef476f793fbdc
pdf-embedded-file PDF EmbeddedFile object 41 at offset 0x52 1164 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 2 eval/decoder/string-building token(s).
deobfuscated.js
a324d1309fba623e019d89551d62d223747719dab38287480d44a021003a6288
deobfuscated-js PDF JavaScript deobfuscation pass 2379 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 2 eval/decoder/string-building token(s).