PDF malware analysis — malicious · f6f1c53e83a86ea6

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: 90eafee1456576ceb4c3b6236a6730bb SHA-1: 55b968bbccf4e1d32a9c02185fafef8f41442891 SHA-256: f6f1c53e83a86ea6325012170aae0a54769b591af65d9375263ba08c6a07fe51

166 Risk Score

Malware Insights

MITRE ATT&CK

T1059.001 PowerShell T1204.002 Malicious File

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 a specific exploit related to `Collab.collectEmailInfo`. The JavaScript is obfuscated using `eval()` and `String.fromCharCode()`, suggesting it's designed to download and execute a second-stage payload. The file's metadata indicates it was created by Scribus, but the exploit and obfuscation point to malicious intent.

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` `d585b0d1649a73a877c607667c6abc3f520b315706c4b8f95ae6da2faad1de63`	pdf-javascript-stream	PDF /JS object 13 at offset 0x3D7	13289 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` `a9c15560288ccadc1422cc907d3e1af8074da38cd98ccdce75387d7757f16d3a`	deobfuscated-js	numeric char-code string decoded JavaScript at offset 0x445	4032 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.