Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 c131b82eb12752bf…

MALICIOUS

RTF / .DOC

35.8 KB
MD5: 894ae8c0a9c22f6ba19b2d105e32a187 SHA-1: 3235cd3831b097c044a8855ca3e787ab9e0e1060 SHA-256: c131b82eb12752bf9d006ce97ac134459ab564d34eea84bc25f471ab197c1bc0
120 Risk Score

Malware Insights

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

The RTF document contains embedded OLE objects that are configured to automatically update and activate. This mechanism is commonly used to deliver and execute malicious payloads. The heuristics indicate the presence of OLE object data, an embedded OLE object, and an object update trigger, strongly suggesting code execution via OLE activation. No document body or script content was available for further analysis, limiting the ability to determine the specific payload or family.

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_off00001dd3.bin
8a87361f56017fa6ef71dd5475d343bafc493e3f46d0fe76c2619338a6b1ebf0
rtf-objdata-decoded RTF \objdata at offset 0x1DD3 4173 bytes