PDF malware analysis — malicious · e44338c12b27bc5d

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: 30403306d2956b92db7f09865f33e400 SHA-1: 61d22951cff5f7d781b511f6d4dacb1aba6fcd8d SHA-256: e44338c12b27bc5df012b312fbd3dc45cda59b818fbd8b29fd3d6b0afbd15b12

168 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 firing 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 technique is indicative of a downloader or exploit kit.

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` `036cb61dcf217689da4a9c07e5f700d5e673e9656e09f301e31301a94f871337`	pdf-javascript-stream	PDF /JS object 13 at offset 0x3D7	14011 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` `46f957e9c54303c5faf342bfb450b1c10b249e017e5c7dfa63e0490a44d0bc87`	deobfuscated-js	numeric char-code string decoded JavaScript at offset 0x445	4260 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.