Malicious RTF — malware analysis report

Static analysis result for SHA-256 c524975ff1bac1ed…

MALICIOUS

RTF

754.1 KB First seen: 2019-04-17
MD5: eed50cb83582d16d51ea8073d4cb5a1c SHA-1: b6b45c90e2f14c935013389baf7f767260703f9d SHA-256: c524975ff1bac1ed21fc74b90621cef036522629c112ce2a16b22a7c782045e5
100 Risk Score

Malware Insights

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

The RTF document contains OLE object data that is forced to activate via \objupdate, indicating an attempt to execute embedded content. This is a common technique for delivering malicious payloads. Without further analysis of the OLE object, the specific family remains unknown.

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_off00000bd9.bin rtf-objdata-decoded RTF \objdata at offset 0xBD9 62914 bytes
SHA-256: 0106736fdf6c4c9b07d571da407915465374acf5cab12663e9d902456cd0ea1d