Malicious PDF — malware analysis report

Static analysis result for SHA-256 c749c8d23d14dce7…

MALICIOUS

PDF

19.79 MB
MD5: 4a963e5ab7463b5ff8510b05c7ee9cac SHA-1: d31a01d49643166b2afb7137ddeeecf8300405d9 SHA-256: c749c8d23d14dce7f2cf70268e87659531d7add00a26f1a071fddbaa988283c8
84 Risk Score

Malware Insights

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

The PDF file exhibits multiple heuristic firings related to JavaScript and encryption, indicating an attempt to conceal malicious content. The presence of PDF_ENCRYPTED_WITH_JS suggests that JavaScript is used to bypass static analysis and hide the true payload. The document body is heavily obfuscated and unreadable, providing no direct clues about the user-facing lure. Therefore, the primary attack pattern involves obfuscation and likely execution of hidden JavaScript.

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

Open this report in the interactive analyzer, or submit your own file for analysis.