Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 de1bca1609416bb5…

MALICIOUS

RTF / .DOC

1.53 MB
MD5: da91d4696bdd31ed8500e0c0c323238a SHA-1: 18c1aa8839e54d11f64e91f4351b21815e1e39ba SHA-256: de1bca1609416bb5a732d0b7c593a0d833cce2d8d78044d065dfceee78faca45
242 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1204.002 Malicious File

The RTF file contains multiple indicators of exploitation targeting the Equation Editor, including CLSID and OLE object data. The presence of excessive hex data within OLE objects suggests a hidden payload. While no scripts were extracted, the structure strongly implies a classic exploit delivery mechanism, likely leading to a secondary payload download or execution.

Heuristics 7

  • Composite Moniker in RTF OLE object high CVE related RTF_COMPOSITE_MONIKER_RELATED
    RTF contains Composite Moniker CLSID in OLE object context, but no nearby scriptlet/SCT payload was confirmed. Treat as related moniker attack-surface evidence rather than proof of CVE-2017-8570 exploitation.
  • Ole10Native stream in RTF OLE object high CVE related RTF_OLE10NATIVE_STREAM
    RTF contains an embedded OLE object with an Ole10Native stream. This is a strong payload-container signal and is related to Word/OLE exploit delivery, but it is not specific enough on its own to assign a CVE.
  • Equation Editor CLSID critical RTF_EQUATION_EDITOR
    Equation Editor OLE CLSID found inside an OLE object — exploited by CVE-2017-11882 / CVE-2018-0802 / CVE-2018-0798
  • \objupdate forces OLE activation high RTF_OBJUPDATE
    RTF contains \objupdate — forces automatic OLE object instantiation when the document is opened, bypassing user interaction. Almost exclusively seen in Equation Editor exploit documents.
  • Large hex data blocks in OLE object high RTF_EXCESSIVE_HEX
    RTF contains ~1603KB of hex-encoded data inside \objdata sections — may hide a payload
  • OLE object data medium RTF_OBJDATA
    RTF contains 2 \objdata section(s) — embedded OLE objects
  • Embedded URL info EMBEDDED_URL
    One or more URLs were extracted from the document. The URL itself is not a detection — context-specific rules above attribute URLs they actually evaluated; this rule lists URLs that were present in the bytes but were not otherwise tied to a specific finding.
    URL https://bit.ly/2S32i6a

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000006fb.bin
d415adbaa0b8ed8fb6552c1271aa7d901f70ffe52d59f1f55a8d93aa04652dfc		 rtf-objdata-decoded RTF \objdata at offset 0x6FB 801872 bytes

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