RTF malware analysis — malicious · a189c6d27861a88a

MALICIOUS

RTF

17.4 KB First seen: 2018-09-04

MD5: f2e6b2f87263a5bf684a1a625365c17d SHA-1: 8c66a5725fb847ec49dc43eb8df98edef8ed7ede SHA-256: a189c6d27861a88a7901f0ebc82ebc136c42416c0697e2c34101fe8d14d674ce

100 Risk Score

Malware Insights

MITRE ATT&CK

T1566.001 Spearphishing Attachment T1203 Exploitation for Client Execution

The RTF file contains embedded OLE object data that is forced to activate via \objupdate. This suggests the file is designed to exploit vulnerabilities or execute embedded code upon opening. While no specific script was extracted, the OLE activation strongly implies a mechanism for downloading and executing a second-stage payload, likely initiated by a spearphishing attachment. The lack of explicit script content prevents a higher confidence score.

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.

Filename	Kind	Source	Size
`objdata_00_off00000ed8.bin`	rtf-objdata-decoded	RTF \objdata at offset 0xED8	4653 bytes
SHA-256: `825096e88fb9e4eb655dd7f6425259618bf25beb201cdb15162963b5663c40d9`

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