Malicious PDF — malware analysis report

Static analysis result for SHA-256 34b1eb4a1142cda1…

MALICIOUS

PDF

4.2 KB
MD5: 9ed25bb4dd0a1da9445634760e1e56a7 SHA-1: 879851012e20d4bd2b766ee7945c38b7dd55d32c SHA-256: 34b1eb4a1142cda1ff67d57feaa99aebe0c7d17a89cc46506d056f53b83678fe
126 Risk Score

Malware Insights

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

The PDF file contains embedded JavaScript that utilizes eval() and String.fromCharCode, indicating obfuscated code execution. The critical CVE-2008-2992 heuristic firing confirms the use of a specific PDF exploit technique involving numeric character codes and JavaScript evaluation. The extracted JavaScript file, 'numeric_charcode_stage_000.js', is likely the second stage of the attack, designed to download and execute further malicious content. The document body is unreadable, but the presence of exploit-related heuristics and embedded scripts strongly suggests a malicious intent.

Heuristics 6

  • 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)
  • 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.

FilenameKindSourceSize
javascript_obj0005_000.js
81a578c2ba941830dabe92bcc840968af4299198b33c292d7de251a85808856d
pdf-javascript-stream PDF /JS object 5 at offset 0x107 21401 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
d4349d9ed90410f3a8b927a2caa468e0a6e37228c1d924e478936e31172f0241
deobfuscated-js numeric char-code string decoded JavaScript at offset 0x115 6301 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).