Malicious PDF — malware analysis report

Static analysis result for SHA-256 c85dc2f0547828f8…

MALICIOUS

PDF

14.3 KB
MD5: 9ff2d502d65275eedff87e991b86346d SHA-1: afb430d67f484ec1364fecc3dab83481d5407de7 SHA-256: c85dc2f0547828f86d0be6645d92819488298e9ac02e2c6be00e5e95801593a1
170 Risk Score

Malware Insights

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

The sample is a PDF file that exploits CVE-2010-0188 via XFA forms. ClamAV also detected it as Js.Exploit.HTML-30, indicating JavaScript-based exploitation. The embedded URL is likely part of the exploit chain. The primary attack pattern involves luring the user into opening a malicious PDF that triggers an exploit, leading to arbitrary code execution.

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/