Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 54dde77a8386235d…

MALICIOUS

RTF / .DOC

16.4 KB
MD5: 7f20ee4d69d67977e6abcb6e5b9ac435 SHA-1: a8156ba92a33d61cd3729f0e8167d8a9b64096c0 SHA-256: 54dde77a8386235db2295846fe639accdcc177057d6bac28d9e2697d669844eb
100 Risk Score

Malware Insights

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

The RTF file contains OLE object data and triggers an OLE activation heuristic, indicating it's designed to exploit OLE vulnerabilities. The presence of ".objdata" and ".objupdate" sections strongly suggests an embedded OLE object is being used to deliver a payload. No readable document body or scripts were extracted, making it difficult to determine the exact user-facing lure or the specific payload, but the mechanism points to code execution.

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_off0000003e.bin
060adf2443d6968379c198ea89e8812dcfe7e8872a2a74f001e46751870739d0
rtf-objdata-decoded RTF \objdata at offset 0x3E 4151 bytes