Malicious PDF — malware analysis report

Static analysis result for SHA-256 84320d40c13a19f1…

MALICIOUS

PDF

9.4 KB
MD5: 519dfa4a4a807bb4c67a0016ab0eb4f9 SHA-1: 880999393406d12099e61e5d79891f1045e5925d SHA-256: 84320d40c13a19f131f0966a1350f9a9c16c06dcbe734678e2951f7e32216444
158 Risk Score

Malware Insights

MITRE ATT&CK
T1059.007 JavaScript T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The PDF file contains obfuscated JavaScript, indicated by PDF_JAVASCRIPT and PDF_JS heuristics, which utilizes eval() and String.fromCharCode. This JavaScript is designed to exploit a client-side vulnerability, likely for executing a secondary payload. The ML classifier also flagged the PDF as malicious. No specific family could be identified, and no direct IOCs like URLs or hashes were extracted from the benign-looking document body.

Machine Learning

  • Nyx PDF Classifier malicious score 0.5949

Heuristics 7

  • PDF JavaScript exploit cluster critical PDF_JS_EXPLOIT_CLUSTER
    PDF combines an executable JavaScript/action surface with exploit staging indicators such as eval/unescape/fromCharCode, XFA script content, or a related CVE pattern. Benign form JavaScript remains low-severity, but this correlated cluster is high-confidence malicious behavior.
  • eval() call high PDF_EVAL
    eval() found — commonly used for obfuscated exploit execution (matched inside decoded stream)
  • 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. (matched inside decoded stream)
  • 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. (matched inside decoded stream)
  • 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://www.w3.org/1999/02/22-rdf-syntax-ns#
    • http://ns.adobe.com/xap/1.0/
    • http://purl.org/dc/elements/1.1/
    • http://ns.adobe.com/xap/1.0/mm/
    • http://ns.adobe.com/pdf/1.3/

Extracted artifacts 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
stream_002_off00000329.bin
618b5430cf3c14a301ec45bb1ccc28ec0f5d79ebb42a296cf093098bf3cfd61f
decompressed-pdf-stream PDF FlateDecoded stream at offset 0x329 5067 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 1 eval/decoder/string-building token(s).
objstm_0024_00.bin
03654aaa7df52c5553edf7d74aef13a6d58a1dd6ace3abbdaaeba947c4265f4a
pdf-objstm-decoded PDF /ObjStm 24 0 obj (inflated) 680 bytes