Malicious PDF — malware analysis report

Static analysis result for SHA-256 f23977b6cb52c590…

MALICIOUS

PDF

14.3 KB
MD5: 8e051f7e102d3fe0269a0584bd24d0dd SHA-1: 1534fbf2f5245e7ed39f7fce58f1a33eac7af287 SHA-256: f23977b6cb52c590536470c0b46911cc9456b8dd99f7e3581a50c1839b618926
170 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1059.001 PowerShell

The PDF file contains an XFA form and triggers a critical heuristic for CVE-2010-0188, indicating an exploit for Adobe Reader. The XFA numeric stager suggests it's designed to evaluate and execute code. The embedded URL is likely part of the exploit chain. The ClamAV detection further confirms its malicious nature. The document body appears to be obfuscated script content, likely responsible for downloading and executing a secondary 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: 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/