PDF malware analysis — malicious · 24adbc76ee8783ae

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: fe19e75d8a585d075dea5c49b612c4d4 SHA-1: fcdc3e48b6439a24e2ff40f1c0dfd5e8c2e1a3f8 SHA-256: 24adbc76ee8783aec5ae7ab2ed478314247219a57b86981c2a4417a75a2c9523

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. The script utilizes eval() and String.fromCharCode, indicating obfuscation. A critical finding is the CVE-2007-5659 exploit, which leverages the Collab.collectEmailInfo method. This exploit is designed to decode and execute JavaScript, likely to download and run a second-stage payload. The presence of obfuscated JavaScript and the specific CVE exploit strongly suggest a malicious intent to compromise the user's system.

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` `f66af512de2b0f8a08e6ab3d2363312e17bf76e7a463302fe1c51fce55c821e1`	pdf-javascript-stream	PDF /JS object 13 at offset 0x3D7	13935 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` `fe258e300aafa38c95ebe48fab5186629245283c1e653ae82ec05bf2bdc2455c`	deobfuscated-js	numeric char-code string decoded JavaScript at offset 0x445	4236 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.