Malicious RTF — malware analysis report

Static analysis result for SHA-256 0a3f025bc69788e0…

MALICIOUS

RTF

14.2 KB First seen: 2018-07-27
MD5: e742774f6482ba29ee85f3bcba4347c6 SHA-1: 6feba335fb57b945c69e6e2617073584cc991fae SHA-256: 0a3f025bc69788e067ec7d3fde24f54d07d8c4ca343e4576cfa4777bdcdfe323
100 Risk Score

Malware Insights

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

The RTF document contains embedded OLE object data, indicated by RTF_OBJDATA and RTF_OLE10NATIVE_STREAM heuristics. The RTF_OBJUPDATE heuristic suggests that the embedded object is designed to be activated automatically, likely leading to the execution of a malicious payload. No specific family could be identified, and no further IOCs were extracted.

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_off00000800.bin rtf-objdata-decoded RTF \objdata at offset 0x800 4157 bytes
SHA-256: dc57e0ef3a0e5781a63b5078917797468e897ddbfabbb0a65482fce01325d39b