Malicious PDF — malware analysis report

Static analysis result for SHA-256 aa58783832af4bfb…

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: 3a3b2ae14c18f71ea08ab418ea819ff4 SHA-1: c38abbb8b0fcc972402b6c3bdcccecca9ade73a3 SHA-256: aa58783832af4bfbb1802862b19a736dcb5ec18880486d5e7a3e02116bb0419c
166 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell T1204.002 Malicious File

The PDF file contains embedded JavaScript triggered by the OpenAction, which is a common technique for exploiting PDF vulnerabilities. The heuristics indicate the use of eval() and String.fromCharCode, along with a specific CVE-2007-5659 exploit targeting the Collab.collectEmailInfo function. This suggests the script is designed to deobfuscate and execute malicious code, likely downloading a secondary payload. No specific family could be identified.

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.

FilenameKindSourceSize
javascript_obj0013_001.js
ac001ae30bf2add7a678d3b6bcce187b66b74c7ffcd7ae518f73166a322f104e
pdf-javascript-stream PDF /JS object 13 at offset 0x3D7 14151 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
2ef7f0ddcf63663f48e8c20a59e34b807e788fb08450831fb24373a9d8153560
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).