PDF malware analysis — malicious · 2f3c7f0d5bcdaae2

MALICIOUS

PDF

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

MD5: b67c7021c67cd2c24423cd78006804bf SHA-1: 930f4645828f6971e180a1773d977d24956f8522 SHA-256: 2f3c7f0d5bcdaae2288c45fdcf293dcca5c6c8cc22f1434eaeb966ee4775369c

166 Risk Score

Malware Insights

MITRE ATT&CK

T1059.001 PowerShell T1204.002 Malicious File

The PDF file contains embedded JavaScript triggered by an OpenAction, which is a common technique for exploiting PDF reader vulnerabilities. The critical CVE-2007-5659 heuristic indicates the use of `Collab.collectEmailInfo` to decode and evaluate obfuscated JavaScript. This script likely downloads and executes a second-stage payload, as suggested by the presence of deobfuscated JavaScript streams. The file's purpose is to deliver further malicious content.

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` `f796cef9e6263875f1f187ccee1c77519382fdbcb4ba4e1d100fd76df0d438d0`	pdf-javascript-stream	PDF /JS object 13 at offset 0x3D7	13429 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` `7b3ed472676c22251da6d88f6243b08ff8f436c5d8c50c8d79a55f9e8221f2fe`	deobfuscated-js	numeric char-code string decoded JavaScript at offset 0x445	4008 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.