Malicious PDF — malware analysis report

Static analysis result for SHA-256 e8c6670d4e20d30c…

MALICIOUS

PDF

28.6 KB
MD5: 36b01c4993349d84c2706310ee226001 SHA-1: a7427af2bdfeb287689a42a2f2b88dfdf8a58459 SHA-256: e8c6670d4e20d30ca8d2a7d647f9b9702c4ca2719c03385aa8cfa5092333eb24
170 Risk Score

Malware Insights

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

The sample is a PDF file that exploits CVE-2010-0188, a vulnerability in Adobe Reader related to XFA forms. The heuristic firings indicate that the file contains an XFA numeric character-table eval stager, which is commonly used to download and execute a second-stage payload. The embedded URL is likely part of this delivery mechanism. ClamAV also detected this file as Pdf.Exploit.Agent-36825.

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.Agent-36825 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Pdf.Exploit.Agent-36825
  • 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/