Malicious PDF — malware analysis report

Static analysis result for SHA-256 23db40dffa52b503…

MALICIOUS

PDF

35.2 KB
MD5: 56087bf5906e94dc1588fb153b80fd7b SHA-1: a41a665e3a2e765e461a46780027e9f07fe8a83f SHA-256: 23db40dffa52b503813591702b11bb83b5aa721e9c05945b97b158c4251d8b4f
102 Risk Score

Malware Insights

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

The PDF file exhibits multiple indicators of malicious activity, including embedded JavaScript, a Flash object, and an embedded file. The presence of JavaScript actions and streams, along with the ASCIIHexDecode filter, suggests an attempt to obfuscate malicious code. The embedded JavaScript file and the embedded binary file are primary artifacts likely used to execute further malicious actions, such as exploiting vulnerabilities or downloading additional payloads. 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 0xE51 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
39f98ff2bc7b15c1a462e303746eac902e8fa3aa0e422a0e185adf3bee67b06c
pdf-javascript-stream PDF /JS object 6 at offset 0x105 10506 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 2 eval/decoder/string-building token(s).