Malicious PDF — malware analysis report

Static analysis result for SHA-256 e40ea3da8915bdcc…

MALICIOUS

PDF

14.3 KB
MD5: 4846d9512b56f0570d78ab92ab5f49d1 SHA-1: 26f4260621c070280c7294f4fdbe9e6f2e8b954d SHA-256: e40ea3da8915bdcc2c08d130a620156456983d53a16ae2aee22cc50ebed08417
170 Risk Score

Malware Insights

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

The PDF file contains an XFA form and exploits CVE-2010-0188, a known vulnerability in Adobe Reader related to LibTIFF processing within XFA forms. ClamAV also detected it as Js.Exploit.HTML-30, indicating embedded JavaScript exploit code. The XFA numeric stager suggests an attempt to evaluate code, likely to download and execute a second-stage payload. The embedded URL is likely 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: 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/