Malicious PDF — malware analysis report

Static analysis result for SHA-256 5dfd660fd479deb1…

MALICIOUS

PDF

14.4 KB
MD5: 605347577e5d162690d6a281d591ee79 SHA-1: 07a746dd09d885e117ffe4f2d07f43c8b819442a SHA-256: 5dfd660fd479deb163d59898eff91f0644f80e39a6375920cc66055e5fcbee93
202 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The file is a PDF containing an XFA form that exploits CVE-2010-0188, a known vulnerability in Adobe Reader for client execution. The XFA form includes a numeric evaluation stager, indicating it's designed to download and execute a secondary payload. The embedded URL, while seemingly benign, is part of the exploit chain.

Machine Learning

  • Nyx PDF Classifier malicious score 1.0000

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/