Malicious PDF — malware analysis report

Static analysis result for SHA-256 c294efdff8190ebe…

MALICIOUS

PDF

72.5 KB
MD5: 93bbc202567c3d873a54796bbbc89bb1 SHA-1: 73589a90da3da16aff47fa7117aa7260211a4972 SHA-256: c294efdff8190ebef906af635c80aec6a8e5575a8ad6a154c08ad0aa482af667
166 Risk Score

Malware Insights

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

The PDF file contains embedded JavaScript that is obfuscated using binary XOR encoding. This script is designed to exploit CVE-2007-5659 in Adobe Reader, specifically targeting the Collab.collectEmailInfo function. The exploit stage is then evaluated, indicating the document's purpose is to deliver a second-stage payload via this exploit.

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
24eea85794de992fde61c29c5f69907babb8fe5bec2fc65ab6eb5070e82969e9
pdf-javascript-stream PDF /JS object 4 at offset 0xC0 73877 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
2d8ff7559f944d35af868e1d63203e8580b1adcae28d367ea8946c53ece32f41
deobfuscated-js binary-XOR decoded JavaScript at offset 0x62AE 1189 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 3 eval/decoder/string-building token(s).