Malicious PDF — malware analysis report

Static analysis result for SHA-256 a0bd9e5cfe677cee…

MALICIOUS

PDF

15.7 KB
MD5: 96d6d24c37fa9b8e7999167610fcd793 SHA-1: 5377654adc49e5cc3a540973b9d2661bf4a418ad SHA-256: a0bd9e5cfe677cee8d75c65c34bc613d9fcc286600524e389cdfc949b4d72474
166 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell T1204.002 Malicious File T1566.001 Spearphishing Attachment

The PDF file contains multiple high-severity heuristics indicating JavaScript execution, including eval() calls and a large comment-padded JavaScript eval stager. ClamAV detection as 'Pdf.Exploit.Agent-36086' further confirms its malicious nature. The embedded JavaScript streams, particularly 'legacy_pdfkit_stage_000.js', are indicative of a stager designed to download and execute further malicious content, a common technique for initial access.

Heuristics 7

  • ClamAV: Pdf.Exploit.Agent-36086 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Pdf.Exploit.Agent-36086
  • eval() call high PDF_EVAL
    eval() found — commonly used for obfuscated exploit execution (matched inside decoded stream)
  • Large comment-padded JavaScript eval stager high PDF_JS_LARGE_COMMENT_PADDED_EVAL
    PDF JavaScript contains a very large stream padded with long random-looking block comments around String.fromCharCode and eval. This is an exploit-kit obfuscation shape used to bury a decoder and recovered stage inside noise, not normal PDF form automation.
  • 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_obj0006_000.js
c36e2bea33c624d95c9179d631728e08b7d676d8b88c9f55aee63e577d0775d7
pdf-javascript-stream PDF /JS object 6 at offset 0x143 425115 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 2 eval/decoder/string-building token(s). Carved artifact contains 42 long base64-like blob(s).
legacy_pdfkit_stage_000.js
4e0704c9bcd70a36a347a90caf28f0a9eb021451266286d3b263b604432f639c
deobfuscated-js double percent-decoded annotation JavaScript at offset 0x143 262144 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 614 long base64-like blob(s).