Malicious PDF — malware analysis report

Static analysis result for SHA-256 f3431fca413333e7…

MALICIOUS

PDF

28.6 KB
MD5: 1f4e274c1c19ccfb854f675dd2b43360 SHA-1: 5f67a5bc2312db6ed57c14ab58a71c1c9b00401e SHA-256: f3431fca413333e711c57d3e98a55529618621bcdef353ef5c9f8efa8caa57e9
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 the CVE-2010-0188 vulnerability, a known exploit targeting Adobe Reader's LibTIFF component via XFA forms. The heuristic firings indicate the presence of an XFA form and a numeric evaluation stager, both associated with this exploit. The embedded URL, while obfuscated, points to an XFA schema, further supporting the exploit vector.

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/