Malicious PDF — malware analysis report

Static analysis result for SHA-256 a0388cf3f55fdb95…

MALICIOUS

PDF

27.03 MB
MD5: 1b94fbecca93f3423a3ed846b5af765f SHA-1: 52f9212751d87de560ba7b351f26a4dbe68e834d SHA-256: a0388cf3f55fdb95c07bf58c91486c0ae1552c63dda16a17ce52050b1b8c676c
114 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell T1566.001 Spearphishing Attachment T1027 Obfuscated Files or Information

The PDF file was flagged as malicious by an ML classifier with high confidence. Heuristics indicate the presence of JavaScript, which is used to encrypt the PDF content, hiding the payload from static analysis. This suggests the document is designed to deliver a malicious script or exploit via JavaScript actions.

Machine Learning

  • Nyx PDF Classifier malicious score 0.9985

Heuristics 5

  • Encrypted PDF carries /JavaScript — payload hidden from static analysis high PDF_ENCRYPTED_WITH_JS
    PDF declares /Encrypt and also references an executable trigger (/JavaScript). Document encryption hides the JavaScript body and stream contents from static scanners — combined with auto-execution indicators this is a known evasion pattern used to deliver weaponised JavaScript that the analyst cannot inspect without the decryption key.
  • ASCIIHexDecode filter (with exploit indicators) medium PDF_FILTER_HEX
    Hex-encoding filter present alongside exploit delivery indicators — often used to hide payload or shellcode bytes
  • 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.
  • Additional-actions dictionary low PDF_AA
    PDF defines /AA (Additional Actions) that references an executable action (JS/JavaScript/Launch/SubmitForm) — can auto-trigger on document or widget events. Form-field calc/format/validate/keystroke handlers in legitimate interactive forms commonly fire this, so it is reported as a low-weight signal; weaponised auto-execution is flagged by stronger rules (PDF_OPENACTION, encrypted-with-JS, etc.)