Malicious PDF — malware analysis report

Static analysis result for SHA-256 a8224bdfe54348ab…

MALICIOUS

PDF

17.9 KB
MD5: 56c018dba91539ec457c11b5b8243571 SHA-1: 85ed1fba63e4217aec931eab2d53c312c477537e SHA-256: a8224bdfe54348abca1614f3a14acbfc957a4a7147606c0e852ac83a0c750724
170 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution

The PDF file contains XFA (XML Forms Architecture) content, which is leveraged by the CVE-2010-0188 exploit. This exploit targets a vulnerability in Adobe Reader's handling of LibTIFF images within XFA forms, allowing for arbitrary code execution. The embedded URL, while seemingly benign, is associated with XFA schemas and may be used in the exploitation chain. The XFA numeric character-table evaluation stager further indicates a malicious intent to execute code.

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