MALICIOUS
210
Risk Score
Malware Insights
MITRE ATT&CK
T1059.007 JavaScript
T1203 Exploitation for Client Execution
T1566.001 Spearphishing Attachment
The critical PDF heuristics indicate the presence of JavaScript exploits within the document, specifically leveraging unescape() calls. The ML classifier strongly suggests maliciousness. The embedded JavaScript is likely designed to download and execute a second-stage payload, a common technique for initial compromise. While specific IOCs like URLs are benign, the exploit cluster and ML score point to a malicious document, likely delivered as a spearphishing attachment.
Machine Learning
- Nyx PDF Classifier malicious score 0.9986
Heuristics 7
-
PDF JavaScript exploit cluster critical PDF_JS_EXPLOIT_CLUSTERPDF 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.
-
Secondary embedded PDF body has suspicious static findings critical POLYGLOT_CHILD_PDF_STATIC_TRIAGEA valid PDF body was found at a nonzero offset inside another container and its carved contents matched PDF exploit or lure heuristics. This catches polyglots where the top-level magic routes to ZIP/OLE while a PDF reader or downstream parser opens the hidden PDF payload.
-
unescape() call high PDF_UNESCAPEunescape() found — often used to decode shellcode in PDF JS exploits
-
JavaScript action low PDF_JAVASCRIPTPDF contains a /JavaScript action. Generic JavaScript is common in benign forms; specific dangerous APIs are scored by separate rules.
-
Embedded JS stream low PDF_JSPDF references a /JS stream. Generic JavaScript is common in benign forms; specific dangerous APIs are scored by separate rules.
-
Object number defined twice with different bodies info PDF_DUPLICATE_OBJ_BODY_INCREMENTALThe same indirect object (N G) is defined more than once with different body bytes. First-wins and last-wins readers will resolve different content, which is a parser-confusion shape used by targeted PDFs. Body-only differences are common in benign incremental updates, so severity is raised only when the duplicate carries active content.
-
Embedded URL info EMBEDDED_URLOne 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.w3.org/1999/02/22-rdf-syntax-ns#
- http://ns.adobe.com/xap/1.0/
- http://purl.org/dc/elements/1.1/
- http://ns.adobe.com/xap/1.0/mm/
- http://ns.adobe.com/pdf/1.3/
Extracted artifacts 3
Files carved from inside the sample during analysis.
| Filename | Kind | Source | Size |
|---|---|---|---|
font_00_sfnt_off000108a5.binaa04ff779405cdf155a2261c4808ac00ed0ad48c86fcb28b9cac7f6a4234b110 |
pdf-font-stream | PDF embedded font (sfnt) at offset 0x108A5 | 3763 bytes |
polyglot_child_pdf_off0000a06e.pdf8f611a4ea7f0a790f7ec605de81c614ecd2793565b4911ebebf667c035c09a7b |
polyglot-child-pdf | Secondary PDF body inside pdf container at offset 0xA06E | 46432 bytes |
polyglot_child_pdf_off00013de1.pdf0b1c923c8a0028794f3a3244dc498786746334f394e41678cc58ffbeb707d0a8 |
polyglot-child-pdf | Secondary PDF body inside pdf container at offset 0x13DE1 | 6125 bytes |
Open this report in the interactive analyzer, or submit your own file for analysis.