Malicious PDF — malware analysis report

Static analysis result for SHA-256 1d6ed1bd7cd4673c…

MALICIOUS

PDF

21.3 KB
MD5: c60e5d86fd84a524ba4c0dcd22601087 SHA-1: e5bbc9d424ab35553ef557f221653ea3c1f256a1 SHA-256: 1d6ed1bd7cd4673c106487527529efdec2383fc5f99c2a88ef749e2aa6f4efdf
170 Risk Score

Malware Insights

MITRE ATT&CK
T1204 Malicious Link T1204.002 Malicious File T1566 Phishing T1566.001 Spearphishing Attachment T1190 Exploit Public-Facing Application

The PDF file contains XFA form elements and triggers a critical heuristic for CVE-2010-0188, indicating an exploit targeting Adobe Reader's LibTIFF component. This exploit is designed to download and execute a second-stage payload. The embedded URL, while seemingly benign, is associated with XFA templates and likely serves as a lure or part of the exploit chain.

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/