Malicious PDF — malware analysis report

Static analysis result for SHA-256 2b47fe852cc0d3d0…

MALICIOUS

PDF

4.7 KB Created: 2010-06-16 08:34:22 Authoring application: Amyuni PDF Creator (via Amyuni PDF Converter version 2.50f)
MD5: cfd2db7ffa1c0a546fb89ec6817579cd SHA-1: 64644978edf3d36a5dd74ab36f01672bf67c5f0b SHA-256: 2b47fe852cc0d3d00ff3e31da3ab0c692a90f9f3a73be4abd4635e2f065e2b35
198 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 JavaScript/JScript T1204.002 Malicious JavaScript

This PDF file was flagged as malicious by multiple critical heuristics, including a PDF JavaScript exploit cluster and a machine learning classifier. The presence of JavaScript actions and an unescape() call strongly suggests the execution of malicious code. The JavaScript appears to be obfuscated, but the core functionality likely involves exploiting a PDF vulnerability to download and execute a second-stage payload. The specific exploit and payload are not fully discernible from the provided evidence.

Machine Learning

  • Nyx PDF Classifier malicious score 0.9991

Heuristics 4

  • 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.
  • Correlated malicious PDF JavaScript signals critical PDF_CORRELATED_MALICIOUS_JS
    PDF JavaScript or auto-action content is corroborated by exploit staging, ML, or suspicious extracted-artifact findings. This correlation promotes old exploit-kit PDFs that otherwise remain in the suspicious band because each individual signal is intentionally weighted conservatively.
  • unescape() call high PDF_UNESCAPE
    unescape() found — often used to decode shellcode in PDF JS exploits
  • 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.