Malicious RTF — malware analysis report

Static analysis result for SHA-256 dad4f92b7d378f6b…

MALICIOUS

RTF

27.4 KB First seen: 2023-05-18
MD5: 01c2fe220d602996255a3760b10a1219 SHA-1: 3bf4b17612698c2529e632f420e6419edbf59dcd SHA-256: dad4f92b7d378f6bd914689cd5a4014486a817d4e0be057e9fc52483cf57dfb4
100 Risk Score

Malware Insights

MITRE ATT&CK
T1566.002 Spearphishing Attachment

The RTF file 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, which is a common technique for executing embedded malicious code. The file's SHA256 hash is provided as a primary indicator.

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_off000019ed.bin
e51967e7f73f34b8bae13c0089cc692801488d63a6b9305a1454a1dc9e9c8738
rtf-objdata-decoded RTF \objdata at offset 0x19ED 4191 bytes