Malicious PDF — malware analysis report

Static analysis result for SHA-256 eef10179058c45df…

MALICIOUS

PDF

11.6 KB
MD5: 6ac05d36e0d0b4bc06f472922f2c3435 SHA-1: b3d436d2b2d905c09a989bc3ea5aff53140e9f0e SHA-256: eef10179058c45dfc3cf639a96fc61e0c3052eee9869fded5324d813f7f9609e
126 Risk Score

Malware Insights

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

The PDF document contains embedded JavaScript that is obfuscated using a hex decoder. The critical heuristic CVE_2007_5659 indicates that the sample leverages the Collab.collectEmailInfo method to achieve code execution. The JavaScript stager, recovered as annotation_subject_callee_hex_stage_000.js, is responsible for decoding and executing the subsequent payload. The primary attack vector is the exploitation of CVE-2007-5659.

Heuristics 6

  • 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)
  • Annotation subject callee-key hex JavaScript stager high PDF_ANNOT_SUBJECT_CALLEE_HEX_STAGER
    PDF JavaScript uses syncAnnotScan()/getAnnots() to read an indirect annotation /Subject stream, percent-decodes it through marker replacement, then uses a callee.toString()-derived key to decode and eval the final 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. (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_obj0007_000.js
c860bd3a1b8438b37e98a599719a1868ae540624631f091272ffef48912644f4
pdf-javascript-stream PDF /JS object 7 at offset 0x19C 579 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 1 eval/decoder/string-building token(s).
annotation_subject_callee_hex_stage_000.js
fc46fab142f37690d59de25df1806990d4efd69c5f3aba8a3b3ae1fa694f8a0f
deobfuscated-js annotation-subject callee-key decoded JavaScript at offset 0x14A 5176 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 5 eval/decoder/string-building token(s).