Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 3e8138c2e3df4bf3…

MALICIOUS

RTF / .DOC

5.8 KB First seen: 2023-05-31
MD5: 8a40bb6b14682736fe06bd11fb985f26 SHA-1: 44e58314a51239eeabd15870c142e7ae7179e011 SHA-256: 3e8138c2e3df4bf31ffd49d89f64916a72c02c612cd080cdec44fdafcae42854
80 Risk Score

Malware Insights

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

The RTF document contains embedded OLE objects, indicated by the RTF_OBJDATA and RTF_OBJEMB heuristics. The RTF_OBJUPDATE heuristic suggests that the embedded object is designed to be automatically activated upon opening the document. This points to a delivery mechanism that relies on user interaction with the embedded object to trigger malicious code execution, likely for downloading and executing a second-stage payload.

Heuristics 3

  • \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
  • 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_off000009e4.bin
2aa80b9b6a025652e89a88bac1f8c34ebccd7e00c2284323a963a721666b50d7
rtf-objdata-decoded RTF \objdata at offset 0x9E4 1639 bytes