Malicious PDF — malware analysis report

Static analysis result for SHA-256 1d8d60d6eaf9c031…

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: 45f594b7e7088812a4548db3609dc70c SHA-1: 7c08f0843478aa56f9ce722fb3c0e42e06d7c38d SHA-256: 1d8d60d6eaf9c031f2c26639d69e062f717aeda7fe51f0eb67841c326651e4c7
166 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 JavaScript T1204.002 Malicious File T1059.003 Windows Command Shell

The PDF file contains embedded JavaScript that is triggered by the OpenAction. Heuristics indicate the use of eval() and String.fromCharCode, along with a specific CVE-2007-5659 exploit targeting the Collab.collectEmailInfo function. This JavaScript is likely used to download and execute a second-stage payload. No specific malware family was 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
3ff2fb866fa5172a8493d232eb7a7fa9aead6a19b5a21438b15a7af01c5d9a86
pdf-javascript-stream PDF /JS object 13 at offset 0x3D7 13327 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
3ac576ab96b354bcd717639d782ba7b6fe3f5fcbc939b9a00bae2ae3b9826c44
deobfuscated-js numeric char-code string decoded JavaScript at offset 0x445 4044 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 5 eval/decoder/string-building token(s).