RTF malware analysis — malicious · 41cbac5847777ba6

MALICIOUS

RTF

9.4 KB First seen: 2019-06-27

MD5: dbb3e64f6598e31a937acf636542962e SHA-1: 5a5406c25439a0b0f3149102056ccbce4e6a9ae3 SHA-256: 41cbac5847777ba6b7dbd7046957ca2409cd86d0b9f0f62e62412ebfd6943471

122 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains an embedded OLE object that is triggered via \objupdate, indicating an attempt to exploit a client-side vulnerability. The extracted artifact 'objdata_00_off00001661.bin' likely contains shellcode or a payload, and the heuristic 'EXTRACTED_FILE_STATIC_TRIAGE' signals a suspicious extracted artifact related to a shellcode URL. This suggests the document is designed to execute malicious code upon opening.

Heuristics 4

Suspicious extracted artifact critical EXTRACTED_FILE_STATIC_TRIAGE

One or more files extracted from inside this sample matched static suspicious-content checks such as script obfuscation, encoded payload blobs, packed data, or execution/download terms.
\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
Embedded URL info EMBEDDED_URL

One or more URLs were extracted from the document. The URL itself is not a detection — see the per-URL labels for which channel (macro, JS, link annotation, document body, ...) reached each URL.
URL http://schemas.microsoft.com/office/word/2003/wordml In RTF body
- http://bit.ly/2NAhXCcIn RTF body

Extracted artifacts 1

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`objdata_00_off00001661.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x1661	1672 bytes
SHA-256: `7519e4af93da3b0c804c61bd54cb1db9fece509e0058ea758d816fac894a23af`
Detection ClamAV: No threats found Obfuscation or payload: likely Static shellcode analysis recovered URL(s): http://bit.ly/2NAhXCc

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