Malicious PDF — malware analysis report

Static analysis result for SHA-256 1ad9472c10438af3…

MALICIOUS

PDF

28.6 KB
MD5: f3ee2c0fc138504cc2207d10c0a5c3a3 SHA-1: cd42dd179316adff78d493fcd3ecd5986ad0f5c1 SHA-256: 1ad9472c10438af3b65db96a2c02a1e0aaa218450fa3359df22d751a8acb812b
170 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1566.001 Phishing: Spearphishing Attachment

The sample is a PDF file that leverages XFA forms to exploit CVE-2010-0188 in Adobe Reader. The XFA numeric character-table eval stager indicates a payload delivery mechanism. ClamAV also detected this file as Pdf.Exploit.Agent-36825, confirming its malicious nature. The embedded URL is likely related to the XFA template but does not appear to be a direct payload hosting site.

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: Pdf.Exploit.Agent-36825 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Pdf.Exploit.Agent-36825
  • 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/