PDF malware analysis — malicious · 286d98d1a5b8d1df

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: 8b0bbb3c99c09e7fd0be97a01c125d93 SHA-1: 3e7eb45997e737524e5d77f660e6daceee30d66f SHA-256: 286d98d1a5b8d1df26c440dd0e49bc041dd50aa0e8f63541787323247d5a9f41

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 with a numeric character-code string decoded JavaScript, which is then evaluated. This suggests the script is designed to download and execute a second-stage payload. No specific family could be identified, but the obfuscated JavaScript and exploit indicate a 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` `cee8dc14463ec7defbdbcb92d9f00600c8a4bd5cf4be67a35faaf5c21df83a53`	pdf-javascript-stream	PDF /JS object 13 at offset 0x3D7	13505 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` `060e51babecb216dbef1a94b9413dc71920f57f79ec4dbc39708b7674a089a27`	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.