Malicious RTF — malware analysis report

Static analysis result for SHA-256 69bf388e2f31538c…

MALICIOUS

RTF

172.8 KB First seen: 2019-12-09
MD5: 20f2a51a1b4c1d804dad1b71ad691aa6 SHA-1: 03db176d5af907077ed9358e400c9f18c9fcf29b SHA-256: 69bf388e2f31538c9a1448cd122cdeed2d2fcc5b8accaa808fcfbe1567e953b5
100 Risk Score

Malware Insights

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

The sample is an RTF file containing OLE object data that is triggered for activation via \objupdate. This indicates the file is designed to exploit OLE object handling to execute embedded code. The specific nature of the payload is not directly discernible from the provided heuristics, but the mechanism strongly suggests a malicious document intended to deliver a secondary payload, likely via a spearphishing attachment.

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_off00000f13.bin rtf-objdata-decoded RTF \objdata at offset 0xF13 52713 bytes
SHA-256: 1ca12d611cde434e2b703cc31b50c033822d14eba16de14c1f723c96581e79b6

Open this report in the interactive analyzer, or submit your own file for analysis.