Malicious RTF — malware analysis report

Static analysis result for SHA-256 fbab4dfccb034a98…

MALICIOUS

RTF

19.3 KB First seen: 2018-09-04
MD5: 015a6b33dcb5b5a64ecbf1e15d89647c SHA-1: 1a727fe8dacfbfecd0aef7d48e1c754ee76bc6f0 SHA-256: fbab4dfccb034a98ba4fae5f6c9d521c65704087e173f39d94b7afc63faf3c30
100 Risk Score

Malware Insights

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

The sample is an RTF document containing OLE object data and an \objupdate directive, indicating an attempt to exploit OLE activation for code execution. The presence of these elements strongly suggests a spearphishing attachment used to deliver a malicious payload. No specific family could be identified from the available evidence.

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_off00001676.bin rtf-objdata-decoded RTF \objdata at offset 0x1676 4667 bytes
SHA-256: 25336cf53772e53e7c89ecf6833e860dda05764e3e29efc12193a71b593abed2