PDF malware analysis — malicious · 6211dc011d546e10

MALICIOUS

PDF

4.3 KB

MD5: 87eed7949e3bf18c5929e0e717f9a9ec SHA-1: d1c2253ff43218596f1496890733899a6f52b520 SHA-256: 6211dc011d546e1076c783a2155083e2e4b1072c0105ea7a4a63b19347ed355a

216 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution T1059.007 JavaScript

This PDF file contains embedded JavaScript that leverages the CVE-2008-2992 vulnerability in Adobe Reader. The JavaScript is heavily obfuscated, but analysis indicates it uses String.fromCharCode and eval() to construct and execute exploit code. The primary goal appears to be arbitrary code execution, likely to download and run a secondary payload.

Machine Learning

Nyx PDF Classifier malicious score 0.9999

Heuristics 7

util.printf — CVE-2008-2992 critical CVE exact CVE_2008_2992

PDF JavaScript calls util.printf() — CVE-2008-2992 is a stack buffer overflow in Adobe Reader triggered by a long format-specifier argument. Widely exploited in the wild after disclosure. (identified after JavaScript deobfuscation)
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.
eval() call high PDF_EVAL

eval() found — commonly used for obfuscated exploit execution (matched inside decoded stream)
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.
String.fromCharCode low PDF_FROMCHARCODE

String.fromCharCode found — used to construct payload strings dynamically. Common in benign JavaScript libraries for codepoint manipulation, so this alone is informational; weaponised use is also caught by the dedicated fromCharCode-stage and exploit-shape rules. (matched inside decoded stream)
Suspicious extracted artifact info EXTRACTED_FILE_STATIC_TRIAGE

One or more files extracted from inside this sample matched static suspicious-content checks such as script obfuscation, encoded payload blobs, packed data, or execution/download terms.

Extracted artifacts 2

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`javascript_obj0005_000.js` `3654f19130a1e4b26f4d78651a3175e5083b0bdd4551d0bd60009c41558d04e8`	pdf-javascript-stream	PDF /JS object 5 at offset 0x107	21085 bytes
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact contains 2 eval/decoder/string-building token(s).
`numeric_charcode_stage_000.js` `223fe3a1455966fc5c3d2f202913a436756acb67909ded3734337ca296ef2b18`	deobfuscated-js	numeric char-code string decoded JavaScript at offset 0x115	6215 bytes
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact contains 3 eval/decoder/string-building token(s). Carved artifact contains 2 long base64-like blob(s).

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