LokiBot — RTF malware analysis

Static analysis result for SHA-256 3781cf44c811a9d9…

MALICIOUS

RTF

1.12 MB First seen: 2019-04-18
MD5: 41fdf17dcc23de061824cbf39d19d1ca SHA-1: a0fa6c23334ec2ad15aed0025382f12dade9600d SHA-256: 3781cf44c811a9d9ee19b7f2982456d1cb979f1e89accb3f8efb8a9819bf56f1
460 Risk Score

Malware Insights

LokiBot · confidence 95%

MITRE ATT&CK
T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF document contains multiple indicators of exploitation, including OLE object data, a composite moniker, and excessive hex data, strongly suggesting the use of CVE-2017-8570. ClamAV detections confirm the presence of LokiBot, a known information stealer and dropper. The exploit likely facilitates the execution of a second-stage payload, consistent with the behavior of droppers.

Heuristics 9

  • Composite Moniker — CVE-2017-8570 (drops SCT script) critical CVE related CVE_2017_8570
    RTF \objdata decodes to OLE data containing the Composite Moniker — CVE-2017-8570 (drops SCT script) CLSID — the vulnerable control/moniker is embedded directly in the document's object stream, the delivery shape of this exploit. RTF objects auto-render when Word opens the file.
  • 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.
  • ClamAV: Win.Dropper.LokiBot-10020561-0 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Win.Dropper.LokiBot-10020561-0
  • PE header (with DOS stub) in hex data critical RTF_MZ_HEX
    Hex-encoded PE (MZ + DOS stub) found inside RTF — likely an embedded executable payload
  • \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 ~1096KB of hex-encoded data inside \objdata sections — may hide a payload
  • OLE object data medium RTF_OBJDATA
    RTF contains 7 \objdata section(s) — embedded OLE objects
  • OlePres presentation stream in RTF OLE object medium RTF_OLEPRES_STREAM
    RTF contains an embedded OLE object with an OlePres presentation stream. OlePres is an OLE presentation marker and is not enough on its own to identify CVE-2025-21298.

Extracted artifacts 6

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00000031.bin rtf-objdata-decoded RTF \objdata at offset 0x31 548044 bytes
SHA-256: cc534903d240398a08fb9ea7d1a4dbc4de57bf0539e94d48f0ff3de5c494a05b
Detection
ClamAV: Win.Dropper.LokiBot-10020561-0
Obfuscation or payload: unlikely
objdata_01_off00114a49.bin rtf-objdata-decoded RTF \objdata at offset 0x114A49 11417 bytes
SHA-256: 5d6cfe4c5d1aa428e7c0f5e3f03a769703c8abf56b2cd296a4c4e881ac0011e7
objdata_02_off0011a3b3.bin rtf-objdata-decoded RTF \objdata at offset 0x11A3B3 381 bytes
SHA-256: 3458e1d85410d8b0a08c68591e0912e582782375d61f43343a9a5d6983b8c436
objdata_03_off0011a6e9.bin rtf-objdata-decoded RTF \objdata at offset 0x11A6E9 788 bytes
SHA-256: 9f474d871d5073e0821f436fc51680b1a4730c0843652540921f90acc5b5f4a5
objdata_04_off0011ad8f.bin rtf-objdata-decoded RTF \objdata at offset 0x11AD8F 2633 bytes
SHA-256: 1feb5f150bb35566d1a01fc59a357dc0ea34bc7498e0ec99bd939f6f848044b0
objdata_05_off0011c2b7.bin rtf-objdata-decoded RTF \objdata at offset 0x11C2B7 4679 bytes
SHA-256: 82391dd064c94b96ac16e2f26524d4d6c5630381aa5a88c7c3d5e8aac77bbfc4

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