Malicious PDF — malware analysis report

Static analysis result for SHA-256 af0914d96051805b…

MALICIOUS

PDF

14.3 KB
MD5: a40fa208ea5f74cf757a523a06724aa6 SHA-1: 68daa6002264737e55594957d154dfa78acfcd7b SHA-256: af0914d96051805be55bd820c6e7756f78e6ee1d32288a14be7c1c3818f9a8e4
170 Risk Score

Malware Insights

MITRE ATT&CK
T1204 Malicious Link T1204.001 Malicious Link: Malicious Link T1059 Command and Scripting Interpreter

The PDF file contains an XFA form and triggers the CVE-2010-0188 exploit, indicating it's designed to compromise Adobe Reader. The embedded URL and the ClamAV detection (Js.Exploit.HTML-30) further support its malicious nature. The document body contains obfuscated JavaScript that appears to be a stager for evaluating XFA numeric expressions, likely to download and execute a second-stage payload.

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: Js.Exploit.HTML-30 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Js.Exploit.HTML-30
  • 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/