Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 63bed4590cc84b03…

MALICIOUS

RTF / .DOC

32.1 KB
MD5: 235db681a2cced19427a7ac9f166756a SHA-1: e9a9aa11805c5b7d9d4cc25d492eda925ecc9c29 SHA-256: 63bed4590cc84b039552202a82d8a3d62cd39b44d084d69a02dd8597dd2287ba
100 Risk Score

Malware Insights

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

The RTF document contains embedded OLE objects, indicated by the RTF_OBJDATA and RTF_OLE10NATIVE_STREAM heuristics. The RTF_OBJUPDATE heuristic suggests that these objects are designed to be activated automatically upon opening the document. This activation likely triggers the execution of a malicious payload, consistent with a spearphishing attachment. No scripts were extracted, but the OLE object's behavior points towards exploitation for client 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 2 \objdata section(s) — embedded OLE objects

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00000c29.bin
5b6dab284f6a7c71b32c4697e1a53dc3e886995ecfde3d22519a7c84c74bca73
rtf-objdata-decoded RTF \objdata at offset 0xC29 4163 bytes