Malicious PDF — malware analysis report

Static analysis result for SHA-256 75b81fe0f9a195df…

MALICIOUS

PDF

734.2 KB
MD5: 1e1359536d0c0da0d7ccf08e790c7730 SHA-1: ca9c026fba7a8947fe3e80da06def2e76ffcf3ab SHA-256: 75b81fe0f9a195dfa4120ca6dc9a650c412fb04f163f2fb8aee84e080ee26dd7
174 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell T1204.002 Malicious File

The PDF file contains embedded JavaScript, flagged by multiple critical heuristics, indicating an exploit attempt. The presence of PDF_XFA and PDF_JAVASCRIPT rules strongly suggests that the document leverages XFA forms to execute malicious JavaScript. This script is likely designed to download and execute a second-stage payload, a common technique for initial access.

Machine Learning

  • Nyx PDF Classifier malicious score 0.9998

Heuristics 6

  • PDF JavaScript exploit cluster critical PDF_JS_EXPLOIT_CLUSTER
    PDF combines an executable JavaScript/action surface with exploit staging indicators such as eval/unescape/fromCharCode, XFA script content, or a related CVE pattern. Benign form JavaScript remains low-severity, but this correlated cluster is high-confidence malicious behavior.
  • Correlated malicious PDF JavaScript signals critical PDF_CORRELATED_MALICIOUS_JS
    PDF JavaScript or auto-action content is corroborated by exploit staging, ML, or suspicious extracted-artifact findings. This correlation promotes old exploit-kit PDFs that otherwise remain in the suspicious band because each individual signal is intentionally weighted conservatively.
  • JavaScript action low PDF_JAVASCRIPT
    PDF contains a /JavaScript action. Generic JavaScript is common in benign forms; specific dangerous APIs are scored by separate rules.
  • Embedded JS stream low PDF_JS
    PDF references a /JS stream. Generic JavaScript is common in benign forms; specific dangerous APIs are scored by separate rules.
  • XFA form low PDF_XFA
    PDF uses XML Forms Architecture — can contain script logic
  • 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://ns.adobe.com/xdp/
    • http://www.xfa.org/schema/xci/3.0/
    • http://www.xfa.org/schema/xfa-template/2.8/
    • http://www.xfa.org/schema/xfa-data/1.0/

Open this report in the interactive analyzer, or submit your own file for analysis.