RTF / .DOC malware analysis — malicious · fa3f69b0ef10ad81

MALICIOUS

RTF / .DOC

1.02 MB

MD5: b3d6fc46b086bd0e46a1cc4ef7221ce9 SHA-1: 1409bc1805b7898b7787a60661b032517ffbbb7e SHA-256: fa3f69b0ef10ad8185f8e6b7b784c78a1fba83ad178c1995b9f2c3d0ea408fa8

220 Risk Score

Malware Insights

MITRE ATT&CK

T1204.002 Malicious File T1566.001 Spearphishing Attachment T1059.005 Visual Basic

The RTF document contains multiple OLE objects, with several heuristics indicating automatic linking and update triggers designed to activate the embedded content. The presence of excessive hex-encoded data within these objects suggests a hidden payload. The 'SE_ENABLE_LURE' heuristic further confirms that the document is designed to prompt the user to enable macros or editing, a common social engineering tactic for malware delivery.

Heuristics 7

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.
Automatically linked OLE object high RTF_OBJAUTLINK

RTF contains \objautlink — an automatically linked OLE object surface that can be updated or activated when Word opens the document.
\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.
Large hex data blocks in OLE object high RTF_EXCESSIVE_HEX

RTF contains ~1037KB of hex-encoded data inside \objdata sections — may hide a payload
OLE object data medium RTF_OBJDATA

RTF contains 4 \objdata section(s) — embedded OLE objects
Embedded OLE object medium RTF_OBJEMB

RTF contains \objemb — embedded OLE object
Macro/content-enable lure medium SE_ENABLE_LURE

Document instructs the user to enable macros or editing — a common technique used by malware droppers to bypass Office macro security settings

Extracted artifacts 4

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`objdata_00_off00000bad.bin` `f7eed903502b22057cdaf12fdbe208a03ceb73608b5d1afaf1ed789391ec220e`	rtf-objdata-decoded	RTF \objdata at offset 0xBAD	408296 bytes
`objdata_01_off0000735c.bin` `92febb63ab2a03bd60957639288d560857f661fa614c3ece96df43e0c90478c9`	rtf-objdata-decoded	RTF \objdata at offset 0x735C	408269 bytes
`objdata_02_off000d692d.bin` `51ef705eef602ac6eb91c2063c8f50d4e54b5e051b60429031d41133bc7df645`	rtf-objdata-decoded	RTF \objdata at offset 0xD692D	2632 bytes
`objdata_03_off000d7ed0.bin` `e8d4fe950caed6dcfde26f4b616825bbe11b93458425974b7d075167f675abf7`	rtf-objdata-decoded	RTF \objdata at offset 0xD7ED0	12297 bytes

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