PDF malware analysis — malicious · 54eef4c5d22f66ba

MALICIOUS

PDF

7.9 KB

MD5: f38184d41de20b279551f0392eb1a44d SHA-1: b93fb427a847d5d290374658637690701878a133 SHA-256: 54eef4c5d22f66ba1e71a7c13532ca1e598bdae4f0e7a2ec27d1d75e003d2f2b

346 Risk Score

Malware Insights

MITRE ATT&CK

T1204.002 Malicious File: User Execution: Malicious File T1059.001 Command and Scripting Interpreter: JavaScript T1071.001 Application Layer Protocol: Web Protocols

The PDF file contains embedded JavaScript that leverages multiple Adobe Reader vulnerabilities, specifically CVE-2009-0927, CVE-2007-5659, and CVE-2008-2992. The JavaScript is heavily obfuscated and uses a custom Base64 decoder to unpack layers of exploit code. This code is designed to execute a shellcode payload, as indicated by the ClamAV signature Js.Exploit.Shellcode-18. The primary intent appears to be the exploitation of the reader to download and execute a secondary malicious artifact.

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` `8746dc4b3ea4ae47d4f169f25207168a789b87bee77ff62fb47450ed2704aa89`	pdf-javascript-stream	PDF /JS object 9 at offset 0xD6	19700 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` `010295dfddb89ab60d1a5ed311bfa7c25f3ea82591f2eb4a1a83a7a0264a9c28`	deobfuscated-js	custom Base64 decoded JavaScript layer 2 (PDF /JS object 9) at offset 0x436	10575 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.