PDF malware analysis — malicious · 130fe00672a94ac0

MALICIOUS

PDF

4.0 KB

MD5: 7450d64174af753be897c37ca71920ea SHA-1: 68cc05b2904300955a4d08b09b9ac7bc76afd77d SHA-256: 130fe00672a94ac09062413918156515fbb7b1260e8ba0c38b9f52926b28c4ed

216 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution T1059.007 JavaScript

The PDF sample contains obfuscated JavaScript that leverages the CVE-2008-2992 vulnerability, specifically using `util.printf` and `String.fromCharCode` to decode and execute exploit code. The deobfuscated JavaScript indicates a pattern of generating and sorting arrays, likely as part of the exploit or payload staging. The ML classifier strongly indicates maliciousness.

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` `04e8fc9dccf560fa976dbb4e7f26d4af92fdc56550e806b6d95a4a4ea8a06ccf`	pdf-javascript-stream	PDF /JS object 5 at offset 0x107	18949 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` `be9174006d39de1b0515cab0051f26afc6a064f89de4c375d7ed69a77677d6cf`	deobfuscated-js	numeric char-code string decoded JavaScript at offset 0x115	5599 bytes
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact contains 3 eval/decoder/string-building token(s).

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