Malicious PDF — malware analysis report

Static analysis result for SHA-256 97e6e4e66fdab9ea…

MALICIOUS

PDF

335.1 KB Created: 2010-11-29 10:29:36 Authoring application: FPDF 1.6
MD5: 5e44cab541c9324d5706e08bf79d2ab9 SHA-1: d0303676b7941b3b061699b6ca3a6aa4b7e3feb6 SHA-256: 97e6e4e66fdab9ea021a8061f564b41c492435c2bd576715529d6f5ac05d13ab
106 Risk Score

Malware Insights

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

The PDF file contains embedded JavaScript, indicated by the PDF_JAVASCRIPT and PDF_JS heuristics. The ClamAV detection of 'Js.Exploit.Shellcode-18' strongly suggests that this JavaScript is malicious and exploits a vulnerability within the PDF reader. The PDF_FILTER_HEX heuristic with exploit indicators further supports this. The primary attack pattern involves leveraging these embedded scripts to achieve a malicious outcome, likely downloading and executing a secondary payload.

Heuristics 7

  • ClamAV: Js.Exploit.Shellcode-18 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Js.Exploit.Shellcode-18
  • 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.
  • XFA form low PDF_XFA
    PDF uses XML Forms Architecture — can contain script logic
  • PDF differential parser failed info PDF_DIFFERENTIAL_PARSE_FAILED
    The cross-check parser (pdfminer.six) failed on this file: PDF differential parser exited 1. Static heuristics still ran and any of their findings above are valid; only the differential cross-check signal is missing.
  • 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://ns.adobe.com/xdp/
    • http://www.xfa.org/schema/xci/2.6/
    • http://www.xfa.org/schema/xfa-template/2.6/