Malicious PDF — malware analysis report

Static analysis result for SHA-256 94fa1814b3fa0e90…

MALICIOUS

PDF

9.3 KB
MD5: b654b9a89a52e1f03a8e12d3e9a6f424 SHA-1: c92f6c7b695108fabeae71ff5afdbbed0c25cbe8 SHA-256: 94fa1814b3fa0e9058e019e6329e8328c10f902020d58da0927a724fe1f93f2a
66 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell

The PDF file contains embedded JavaScript, indicated by multiple heuristic firings including PDF_JAVASCRIPT, PDF_JS, and PDF_EVAL. The JavaScript stream at offset 0x10CC is obfuscated and uses String.fromCharCode, suggesting an attempt to hide malicious code. While no URLs were found to be malicious, the presence of obfuscated JavaScript points to a likely attempt to download and execute a second-stage payload or perform other malicious actions.

Heuristics 6

  • 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. (matched inside decoded stream)
  • 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. (matched inside decoded stream)
  • 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.
  • Embedded URL info EMBEDDED_URL
    One or more URLs were extracted from the document. The URL itself is not a detection — see the per-URL labels for which channel (macro, JS, link annotation, document body, ...) reached each URL.
    URL http://www.w3.org/1999/02/22-rdf-syntax-ns#
    • http://ns.adobe.com/xap/1.0/
    • http://purl.org/dc/elements/1.1/
    • http://ns.adobe.com/xap/1.0/mm/
    • http://ns.adobe.com/pdf/1.3/

Extracted artifacts 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
stream_002_off00000328.bin
349effe730260b11a68be04fe3a2309f7b14cbe03c5e542478cfd260d1b1156f
decompressed-pdf-stream PDF FlateDecoded stream at offset 0x328 4918 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 1 eval/decoder/string-building token(s).
objstm_0024_00.bin
a7b97b3b8e9ae4df075fd13b089a026381aa51472c7b0b5d5a8553af4fc8b54a
pdf-objstm-decoded PDF /ObjStm 24 0 obj (inflated) 684 bytes