Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 227271a1c7928e92…

MALICIOUS

RTF / .DOC

34.0 KB First seen: 2021-10-11
MD5: dce1f11e0536192d09a3de13e0cfd7cb SHA-1: 0fca1bdb967984685ad7d499c1ecbe2a56cbebac SHA-256: 227271a1c7928e925f85a48d80853ab380962dac81155d6b9234c32ab2764762
120 Risk Score

Malware Insights

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

The RTF document contains embedded OLE objects that are configured to automatically update and activate. This technique is commonly used to execute embedded code or launch external payloads upon opening the document. The heuristics indicate the presence of OLE object data and a native stream within the OLE object, suggesting the embedded content is intended to be executed. The specific attack pattern is likely related to social engineering to trick the user into opening the document, leading to the execution of malicious code.

Heuristics 4

  • 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
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000019bb.bin
a130dc956e1ba2f95d8784989ef3c778c8a3f6aa54aba2bc327e642f427bce25
rtf-objdata-decoded RTF \objdata at offset 0x19BB 4177 bytes