PDF malware analysis — malicious · 6c89050ec800f602

MALICIOUS

PDF

4.3 KB

MD5: f235fc4c09441c4c9c107d0a31d2a81c SHA-1: f9fd4b6f75325b1027c2111c109481b024cd0701 SHA-256: 6c89050ec800f6022d2da0f0737fe6401af0e997cd1f15dcaa769778a7b55b94

216 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution T1059.007 JavaScript

The PDF sample contains embedded JavaScript that leverages the CVE-2008-2992 vulnerability (util.printf) to achieve code execution. The JavaScript is heavily obfuscated, but analysis indicates it reconstructs and evaluates further JavaScript, likely to download and execute a secondary payload. The ML classifier strongly indicates malicious intent.

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` `cd108e8993afc0937d1da459e91756971056484356abf216094d8c83b4b1cbd2`	pdf-javascript-stream	PDF /JS object 5 at offset 0x107	22338 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` `12f7232a95d44c1050912e5347b5a9fdc856f3f1b30086ea230131c6c616b547`	deobfuscated-js	numeric char-code string decoded JavaScript at offset 0x115	6578 bytes
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact contains 3 eval/decoder/string-building token(s). Carved artifact contains 1 long base64-like blob(s).

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