Malicious PDF — malware analysis report

Static analysis result for SHA-256 1f9a4cb646684831…

MALICIOUS

PDF

15.7 KB
MD5: a6473c4a78c7da15b035fb71230745e3 SHA-1: 1bcf8db9345a7edad015acbfd1015ae4c710cf84 SHA-256: 1f9a4cb646684831b2aa2ff01df58b7b4b7471c602dd9eaeb42b9534eba61e20
166 Risk Score

Malware Insights

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

The PDF file contains multiple JavaScript streams, including a large comment-padded eval stager. Heuristics indicate the use of eval() and String.fromCharCode, common techniques for obfuscating malicious JavaScript. The ClamAV detection of 'Pdf.Exploit.Agent-36086' strongly suggests exploitation of a known PDF vulnerability. The embedded JavaScript is likely responsible for downloading and executing a secondary payload, although the specific URLs or commands are not directly extractable from the provided evidence.

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
6c28fc37300bcc116e4e01c7d78fd4f2f3e27f351d95b84d7a65be6d47967af2
pdf-javascript-stream PDF /JS object 6 at offset 0x143 425648 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
02059d52262317ed88dfbfbf6871cacbd1b30d23268efc858af5fed00726adff
deobfuscated-js double percent-decoded annotation JavaScript at offset 0x143 262144 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 719 long base64-like blob(s).