Malicious RTF — malware analysis report

Static analysis result for SHA-256 17f02f92a25f2dfe…

MALICIOUS

RTF

14.1 KB First seen: 2019-08-04
MD5: bd320a5e207e5b78f3c5634cd480445a SHA-1: 3b12cf7314efa57f0a0ce7dc801fdcc3d0d98301 SHA-256: 17f02f92a25f2dfe2ce314c6a8dea02dd7e0e3013f3ae5339d2d6baf04bd2dd9
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_off000007ff.bin rtf-objdata-decoded RTF \objdata at offset 0x7FF 4156 bytes
SHA-256: 423d4fb5623406cbe6114c65f8c39090a5f53d6fe89c75f65cb7612a55143b11