Malicious PDF — malware analysis report

Static analysis result for SHA-256 9b0848eb28157e8c…

MALICIOUS

PDF

74.3 KB
MD5: 8587ec72a3dc0121df2dbc75e7ab8061 SHA-1: f96926cdb3824b743260d22e8d07dc6ee33b0332 SHA-256: 9b0848eb28157e8c6c334b239cc1deb852c205089b0c6b7be81152212c7e0608
166 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell T1204.001 Malicious Link T1071.001 Web Protocols

The PDF file contains embedded JavaScript that utilizes the Collab.collectEmailInfo method, indicative of the CVE-2007-5659 exploit. This exploit is used to download and execute a second-stage payload. The JavaScript is obfuscated using binary XOR encoding, and the recovered stage is also JavaScript. The primary attack vector is the exploitation of a known Adobe Reader vulnerability.

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)
  • eval() call high PDF_EVAL
    eval() found — commonly used for obfuscated exploit execution
  • Binary-XOR JavaScript stager high PDF_BINARY_XOR_JS_STAGER
    PDF JavaScript stores viewer-version payload branches as long binary digit strings, XORs each bit pair, converts 8-bit chunks with String.fromCharCode, and evals the recovered exploit stage.
  • 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.
  • 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_obj0004_000.js
9cc769b69e40dbf4511499caa24150ba893cd6c09519f44a76920d9c5d38638f
pdf-javascript-stream PDF /JS object 4 at offset 0xC0 75706 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 3 eval/decoder/string-building token(s). Carved artifact contains 6 long base64-like blob(s).
binary_xor_stage_000.js
e3befa633cdc2e029834535f47d1027ce5aa7702bda18252600be2b2ae76328e
deobfuscated-js binary-XOR decoded JavaScript at offset 0x3D7 1231 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 3 eval/decoder/string-building token(s).