PDF malware analysis — malicious · c1bd79f8ec36e5f0

MALICIOUS

PDF

3.6 KB Created: 2008-31-20 53:85:00 Authoring application: Scribus 1.3.3.12 (via Scribus PDF Library 1.3.3.12)

MD5: 06e558adb99e6c8c3c900a4ea8f81c90 SHA-1: c7f3cc4e3a55b2abaad686adfea135729dbf50e0 SHA-256: c1bd79f8ec36e5f08dde56a6e031a21323207be812f39999ab50d9cb5d4dc441

166 Risk Score

Malware Insights

MITRE ATT&CK

T1059.001 JavaScript/JScript T1204.002 Malicious File T1566.002 Spearphishing Attachment

The PDF file contains embedded JavaScript that is triggered by the OpenAction feature, a common technique for exploiting PDF vulnerabilities. The critical heuristic firing for CVE-2007-5659 indicates the use of `Collab.collectEmailInfo` with a decoded JavaScript string that is then evaluated. This suggests the script is designed to download and execute a second-stage payload, making it a downloader. The presence of obfuscated JavaScript streams further supports this conclusion.

Heuristics 7

Collab.collectEmailInfo — CVE-2007-5659 critical CVE exact CVE_2007_5659

PDF JavaScript calls Collab.collectEmailInfo — CVE-2007-5659 is a buffer overflow in Adobe Reader triggered by a long argument or heap-sprayed message field passed to Collab.collectEmailInfo(). Part of a series of Acrobat JS API exploits. (identified after JavaScript deobfuscation)
OpenAction trigger high PDF_OPENACTION

PDF has an /OpenAction — code runs automatically when opened
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_obj0013_001.js` `4f633bf43339ee0d3e140e77d50a48148480f9429bea45e5becf94dc96b3fcc0`	pdf-javascript-stream	PDF /JS object 13 at offset 0x3D7	14011 bytes
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact contains 3 eval/decoder/string-building token(s).
`numeric_charcode_stage_000.js` `e4706d1c8747e9cabc2d6abff0288cc508128a34803741e427506ff5dfa9dc6e`	deobfuscated-js	numeric char-code string decoded JavaScript at offset 0x445	4260 bytes
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact contains 5 eval/decoder/string-building token(s).

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