Malicious PDF — malware analysis report

Static analysis result for SHA-256 6ad33db8a4b75297…

MALICIOUS

PDF

21.4 KB
MD5: 11beeed7fba3bd936becca2f7dc6ec89 SHA-1: 49a44a1418ebfd8343dab2d15ffb8d0e1f6967b4 SHA-256: 6ad33db8a4b75297f7f05b1dc8680118fec1186a3339b16773b7a11eec6cc2b7
202 Risk Score

Malware Insights

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

The sample is a PDF file identified as malicious by multiple engines, including ClamAV and an ML classifier. It contains an XFA form that leverages the CVE-2010-0188 vulnerability, a known exploit for Adobe Reader. The XFA numeric stager indicates the presence of code designed to evaluate and execute a payload, likely downloaded or embedded within the document.

Machine Learning

  • Nyx PDF Classifier malicious score 1.0000

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