Malicious PDF — malware analysis report

Static analysis result for SHA-256 3073084ae3eb1855…

MALICIOUS

PDF

14.3 KB
MD5: 79a0a3f4b3171949761eb337bc8c2752 SHA-1: d18ff1bdab9319a9492ee7a01b75dc727546d977 SHA-256: 3073084ae3eb18553702048fa132e74b2fdbca48415b7dd07bfc19f5af232e2e
170 Risk Score

Malware Insights

MITRE ATT&CK
T1204 Malicious Link T1204.001 Malicious Link: Malicious Link T1204.002 Malicious Link: Malicious File

The PDF file contains an XFA form and triggers critical heuristics for CVE-2010-0188, an Adobe Reader LibTIFF XFA image exploit. ClamAV also detected it as Js.Exploit.HTML-30. The embedded URL, while seemingly benign, is part of the XFA structure and may be used in the exploit chain. The XFA numeric stager suggests an attempt to evaluate code within the document.

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/