Malicious PDF — malware analysis report

Static analysis result for SHA-256 0fccac3869a49d4b…

MALICIOUS

PDF

17.9 KB
MD5: dd2b30dddeb997cf396d620bd292bd40 SHA-1: e710ec7d3c61dafa10eadacd681ce70a2bd59482 SHA-256: 0fccac3869a49d4be54061cab5bf53cc948e9606d34b45619ef37c9d7eef595d
202 Risk Score

Malware Insights

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

The file is a PDF containing an XFA form that leverages the CVE-2010-0188 vulnerability in Adobe Reader. This exploit is designed to execute arbitrary code, likely to download and run a second-stage payload. The presence of XFA and the specific CVE strongly indicate a malicious intent to compromise the user's system.

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