MALICIOUS
262
Risk Score
Malware Insights
MITRE ATT&CK
T1203 Exploitation for Client Execution
T1566.001 Spearphishing Attachment
The RTF file contains multiple indicators of exploitation, including OLE object data, Equation Editor CLSID, and a composite moniker, all pointing to the exploitation of a vulnerability in Microsoft Equation Editor. The heuristic 'EXTRACTED_FILE_STATIC_TRIAGE' specifically flags a suspicious extracted artifact with 'Shellcode URL', indicating the file's intent to download a secondary payload. The embedded URL, though marked as benign, is still included as a potential IOC given the context of the exploit.
Heuristics 7
-
Equation Editor CLSID critical CVE likely RTF_EQUATION_EDITOREquation 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 RTF_COMPOSITE_MONIKER_RELATEDRTF 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 RTF_OLE10NATIVE_STREAMRTF 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_TRIAGEOne 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_OBJUPDATERTF 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_OBJDATARTF contains 2 \objdata section(s) — embedded OLE objects
-
Embedded URL info EMBEDDED_URLOne 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/3gcM2I4 In RTF body
Extracted artifacts 2
Files carved from inside the sample during analysis.
| Filename | Kind | Source | Size |
|---|---|---|---|
objdata_00_off00525deb.bin |
rtf-objdata-decoded | RTF \objdata at offset 0x525DEB | 802004 bytes |
SHA-256: 31d0e115bc7d61bd543bb83a04eeca4a895ee2c6c2d3c55fa4ad235cff576981 |
|||
|
Detection
ClamAV:
No threats found
Obfuscation or payload:
likely
Static shellcode analysis recovered URL(s): https://bit.ly/3gcM2I4
|
|||
objdata_01_off00526012.bin |
rtf-objdata-decoded | RTF \objdata at offset 0x526012 | 63 bytes |
SHA-256: 42d9af0323fb97aca6e24db96944bb9329e910997aef5ab319c3e8db0d113cfb |
|||
Open this report in the interactive analyzer, or submit your own file for analysis.