Malicious PDF — malware analysis report

Static analysis result for SHA-256 d0693f165a6aaa01…

MALICIOUS

PDF

29.8 KB
MD5: 45c16e3f940f3bbe8bfcf2a499e77f2f SHA-1: ab360688425d97604a07481877aa6be45cb11b28 SHA-256: d0693f165a6aaa01fc26a8581b966140f4452cbd901b3602897af4cb24a23af8
82 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 JavaScript actions and embedded JS streams suggests an attempt to execute code. The RichMedia heuristic further points to potentially exploitable content. While the document body is largely unreadable, the combination of these heuristics indicates a likely attack pattern involving the exploitation of PDF vulnerabilities or the delivery of a secondary payload.

Heuristics 8

  • RichMedia (Flash) high PDF_RICHMEDIA
    PDF contains /RichMedia (Adobe Flash) which is a historic exploit vector
  • 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
4d4d42d908c48737d0cbe1f33c14f197803950e6ff47f9c0f13e1d51a231494d		 pdf-embedded-file PDF EmbeddedFile object 16 at offset 0x8CA 53991 bytes
javascript_obj0006_000.js
2175b414a0bd1efcaf355467dbc03a8487fd926bd7e3aa7094a50eafd823997d		 pdf-javascript-stream PDF /JS object 6 at offset 0x106 11498 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 239 eval/decoder/string-building token(s).

Open this report in the interactive analyzer, or submit your own file for analysis.