Malicious PDF — malware analysis report

Static analysis result for SHA-256 e4cf3ec5e0e18ff4…

MALICIOUS

PDF

35.2 KB
MD5: 4ff5a321a05d36a098282006dc1fb893 SHA-1: 7acea06d1560d16698122b6a285310f98e7eacd9 SHA-256: e4cf3ec5e0e18ff4a17810421015edaacd38a5feb24f36eed184e7e59b27dce6
102 Risk Score

Malware Insights

MITRE ATT&CK
T1059.001 PowerShell T1559.002 Component Object Model Hijacking

The PDF file exhibits multiple indicators of malicious intent, including embedded JavaScript and RichMedia (Flash) content. The presence of `String.fromCharCode` and ASCIIHexDecode filters suggests obfuscation techniques commonly used to hide malicious code. The embedded JavaScript stream and the extracted `embedded_file_obj0016.bin` are likely components of a multi-stage attack, potentially leading to the download and execution of further malware. The confidence is moderate due to the lack of specific script content analysis in the provided evidence.

Heuristics 9

  • RichMedia (Flash) high PDF_RICHMEDIA
    PDF contains /RichMedia (Adobe Flash) which is a historic exploit vector
  • ASCIIHexDecode filter (with exploit indicators) medium PDF_FILTER_HEX
    Hex-encoding filter present alongside exploit delivery indicators — often used to hide payload or shellcode bytes
  • 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.
  • Embedded file low PDF_EMBEDDED
    PDF embeds a file attachment — could carry an executable or another weaponised document as a nested payload
  • XFA form low PDF_XFA
    PDF uses XML Forms Architecture — can contain script logic
  • 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://ns.adobe.com/xdp/
    • http://www.xfa.org/schema/xci/2.6/
    • http://www.xfa.org/schema/xfa-template/2.6/

Extracted artifacts 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
embedded_file_obj0016.bin
8f9c84c8c00bc62ae296a81fac6640aa852ea67548abc1bd639aa0da1a1696c4
pdf-embedded-file PDF EmbeddedFile object 16 at offset 0xE33 27347 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 7.99, consistent with packed or encrypted content.
javascript_obj0006_000.js
d9bb95b65af8d1b3c0c06f35ac8acdcb020442adb167372f0aff95deaeded6e9
pdf-javascript-stream PDF /JS object 6 at offset 0x105 10476 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 2 eval/decoder/string-building token(s).