Malicious PDF — malware analysis report

Static analysis result for SHA-256 e47655c1b2aafac3…

MALICIOUS

PDF

18.2 KB
MD5: 03f4636866492209b56762ccc7f74a1f SHA-1: 2af7e6966f21045ce3a35eb4973db29e896e4903 SHA-256: e47655c1b2aafac343e0d31b361082ec6edde6204efb5b16db9b267329f82970
174 Risk Score

Malware Insights

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

The PDF file contains embedded JavaScript, indicated by multiple heuristic firings including PDF_JAVASCRIPT, PDF_JS, and PDF_FROMCHARCODE. The PDF_JS_EXPLOIT_CLUSTER and PDF_CORRELATED_MALICIOUS_JS firings, along with a high ML classifier score, strongly suggest that this JavaScript is malicious and intended to exploit vulnerabilities within the PDF reader. The primary attack pattern involves leveraging these JavaScript exploits to execute a payload.

Machine Learning

  • Nyx PDF Classifier malicious score 1.0000

Heuristics 5

  • 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.
  • 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.
  • 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.