Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 14f7f2a27376e84b…

MALICIOUS

RTF / .DOC

83.6 KB
MD5: 749311f0d56d4cb2d3ad91ce5f9a610b SHA-1: 3e4018c9956e673ae04cdebee195b273fe9c45ee SHA-256: 14f7f2a27376e84b36fd98c109a7d45321385443b7f1f737be7976584aa07a69
100 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1203 Exploitation for Client Execution

The RTF document contains OLE object data that is configured to activate automatically upon opening, as indicated by the RTF_OBJUPDATE heuristic. This mechanism is commonly used to embed and execute malicious payloads, suggesting an attempt to exploit the user's system via a spearphishing attachment. No specific family could be identified.

Heuristics 3

  • 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.
  • \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.
  • OLE object data medium RTF_OBJDATA
    RTF contains 1 \objdata section(s) — embedded OLE objects

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000005a6.bin
06a3e6a37057c5e8bfcf6f102ed314e544472e7f166db7590dcaffb89b1edfca
rtf-objdata-decoded RTF \objdata at offset 0x5A6 4172 bytes