PDF malware analysis — malicious · d54b64a6354b77e1

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: 086c09fc4db5b3e8f66e4af997c4b928 SHA-1: d1573b39138d4f452f81c18cd1f7ac3466f1c509 SHA-256: d54b64a6354b77e1782e7763bb3ff67931514a780baf875a085b3ce4b1fd99d2

166 Risk Score

Malware Insights

MITRE ATT&CK

T1059.001 JavaScript T1204.001 Malicious Link T1566.001 Spearphishing Attachment T1204.002 Malicious File

The PDF file contains embedded JavaScript that is triggered by the OpenAction. Heuristics indicate the use of eval() and String.fromCharCode, along with a critical finding for CVE-2007-5659 (Collab.collectEmailInfo). This suggests the script is designed to deobfuscate and execute malicious code, likely downloading a secondary payload. No specific family could be identified, but the attack pattern is consistent with PDF-based exploit delivery.

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` `d3efea71cab9a8d75623df261ea189449a374d2a2cd4b2ec3d926f35e67eef7e`	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` `92bc6c1f501128af132078d44f79286b8fb4bec9e95d351faff58e83b9cf057c`	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.