PDF malware analysis — malicious · c9427ed6a3c37102

MALICIOUS

PDF

7.6 KB

MD5: aee48cef9f20f89a12bcaee949593a63 SHA-1: dc70f44351176f8df8f894f87977f3fc9bc60a3d SHA-256: c9427ed6a3c37102cb3a33fb29196408d7f63db21983f74564d5f9bf6dc6436f

346 Risk Score

Malware Insights

MITRE ATT&CK

T1059.001 JavaScript/JScript T1204.001 Malicious Link/Object T1204.002 User Execution: Malicious File

The PDF file contains embedded JavaScript that is heavily obfuscated and utilizes custom Base64 decoding. This script exploits multiple Adobe Reader vulnerabilities, specifically targeting CVE-2009-0927 (Collab.getIcon), CVE-2007-5659 (Collab.collectEmailInfo), and CVE-2008-2992 (util.printf). The primary function of the script is to decode and execute a second-stage payload, as indicated by the ClamAV detection 'Js.Exploit.Shellcode-18' on an extracted artifact. The attack pattern is consistent with a drive-by download or exploit-based document delivery.

Heuristics 10

Collab.getIcon — CVE-2009-0927 critical CVE exact CVE_2009_0927

PDF JavaScript calls Collab.getIcon — CVE-2009-0927 is a stack buffer overflow in Adobe Reader triggered by Collab.getIcon() with a crafted argument. Allows arbitrary code execution. (identified after JavaScript deobfuscation)
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)
util.printf — CVE-2008-2992 critical CVE exact CVE_2008_2992

PDF JavaScript calls util.printf() — CVE-2008-2992 is a stack buffer overflow in Adobe Reader triggered by a long format-specifier argument. Widely exploited in the wild after disclosure. (identified after JavaScript deobfuscation)
ClamAV detection on extracted artifact critical EXTRACTED_FILE_CLAMAV

ClamAV flagged at least one file extracted from inside this sample. Even when the wrapping document carries no AV detection of its own, a hit on the carved artifact is a strong indicator the sample is a delivery vehicle.
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.

Filename	Kind	Source	Size
`javascript_obj0009_000.js` `37e2066d315961b7664689379a16ec390b81120891829120eb66f62e1aef5728`	pdf-javascript-stream	PDF /JS object 9 at offset 0xD6	19644 bytes
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact contains 4 eval/decoder/string-building token(s). Carved artifact contains 1 long base64-like blob(s).
`custom_b64_stage_000.js` `dca72ca0787bbc1ab77c907603b8dc5fc46e0a78ff6ec3b9c6538364a7659a41`	deobfuscated-js	custom Base64 decoded JavaScript layer 2 (PDF /JS object 9) at offset 0x450	10526 bytes
Detection ClamAV: Js.Exploit.Shellcode-18 Obfuscation or payload: likely Carved artifact contains 9 eval/decoder/string-building token(s).

Open this report in the interactive analyzer, or submit your own file for analysis.