RTF malware analysis — malicious · 62323b23f68d0a4f

MALICIOUS

RTF

9.72 MB First seen: 2021-06-17

MD5: 93a192474ec0b317144d5a286d8b7133 SHA-1: 08cddb8d39e999ca8ea7015ab2a613a3685d68f8 SHA-256: 62323b23f68d0a4fc39283c9dbde1e19e6563521f7867ebbdd136a226f20e475

262 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution

The RTF file contains multiple indicators of exploitation, including OLE object data, Equation Editor CLSID, and a Composite Moniker. The critical heuristic 'EXTRACTED_FILE_STATIC_TRIAGE' specifically signals a suspicious extracted artifact with shellcode and a URL. This suggests the file is designed to exploit a vulnerability, likely in the Equation Editor, to download and execute a secondary payload from the provided URL.

Heuristics 7

Equation Editor CLSID critical CVE likely RTF_EQUATION_EDITOR

Equation Editor OLE CLSID found inside an OLE object — exploited by CVE-2017-11882 / CVE-2018-0802 / CVE-2018-0798
Composite Moniker in RTF OLE object high CVE related RTF_COMPOSITE_MONIKER_RELATED

RTF contains Composite Moniker CLSID in OLE object context, but no nearby scriptlet/SCT payload was confirmed. Treat as related moniker attack-surface evidence rather than proof of CVE-2017-8570 exploitation.
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.
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 2 \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 https://bit.ly/3x4FIta In RTF body

Extracted artifacts 2

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`objdata_00_off00748fb5.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x748FB5	802004 bytes
SHA-256: `f8644a95bc366a9c210e378fe1995769aa061fbbe645995f8edf154dd9ae3824`
Detection ClamAV: No threats found Obfuscation or payload: likely Static shellcode analysis recovered URL(s): https://bit.ly/3x4FIta
`objdata_01_off007491dc.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x7491DC	63 bytes
SHA-256: `42d9af0323fb97aca6e24db96944bb9329e910997aef5ab319c3e8db0d113cfb`

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