Malicious PDF — malware analysis report

Static analysis result for SHA-256 cab0d5dfc88a1f92…

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: c54859ae4e779daa656f9eb704ce9cfc SHA-1: ee9db4d4d580b084edfb5829e4358b3002283130 SHA-256: cab0d5dfc88a1f928d38c83494d7d6e20d85640bd69f8e0914b8b99a7b9eb03a
166 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 JavaScript T1204.002 Malicious JavaScript 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 suggests the script is designed to deobfuscate and execute a malicious payload, likely a downloader. The extracted JavaScript files confirm the presence of obfuscated code and potential exploit vectors.

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
d1f664e0de53edb6cf597e08f5cbeb4d524cfc22a7e300e5de739c039f8c7b5c
pdf-javascript-stream PDF /JS object 13 at offset 0x3D7 13543 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
d373e25b6f5f8c5d51e48d230aab2ca55624bce3c87ac0b2ceefb43dc26e7667
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).