Malicious RTF — malware analysis report

Static analysis result for SHA-256 8112981b1610afe0…

MALICIOUS

RTF

14.1 KB First seen: 2018-11-13
MD5: 701ee3acc6fa117b9f2cfb9840391721 SHA-1: ed936d4d57485d32efb7bedcf397964f5e6850ec SHA-256: 8112981b1610afe0b028299dd84f1bd669ad714eed71db5bbba38b136e478f8b
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 4146 bytes
SHA-256: 89009c0a8db74ca61bcb7d7e9dd772bceb6080bde7b09e9cf2427dca5b34e57d