Malicious PDF — malware analysis report

Static analysis result for SHA-256 2e30f3296f8a2199…

MALICIOUS

PDF

14.4 KB
MD5: dde8a0db7b1929d88760d68ab23043bf SHA-1: 310c086fa7c33ebb496f651bb6f9ee6cd30bbfa0 SHA-256: 2e30f3296f8a21994005ae08cac159ee589d8b1c5b6c6cab7bbead4a86e4085b
170 Risk Score

Malware Insights

MITRE ATT&CK
T1204.002 Malicious File: User Execution: Malicious Attachment T1059.001 Command and Scripting Interpreter: PowerShell

The sample is a PDF file that leverages XFA forms to exploit CVE-2010-0188 in Adobe Reader. The ClamAV detection 'Js.Exploit.HTML-30' suggests the exploit payload likely involves JavaScript. The embedded URL is related to XFA schemas, which is consistent with the exploit vector. The document body contains obfuscated JavaScript-like code that appears to be part of the exploit stager.

Heuristics 6

  • Adobe Reader LibTIFF XFA image exploit — CVE-2010-0188 critical CVE likely CVE_2010_0188
    PDF contains the CVE-2010-0188 exploit template: XFA JavaScript heap-spray setup, a generated TIFF image payload, and assignment of that TIFF data to an XFA image field rawValue to trigger Adobe Reader's LibTIFF parser.
  • ClamAV: Js.Exploit.HTML-30 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Js.Exploit.HTML-30
  • XFA numeric character-table eval stager high PDF_XFA_NUMERIC_EVAL_STAGER
    PDF XFA initialize script reads numeric form data from rawValue, maps the values through a short character table, and evals the reconstructed stage. This is an exploit-kit staging technique even when the final decoded layer remains encoded.
  • 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 failed: PSEOF. 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://www.xfa.org/schema/xfa-template/2.5/