Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 5eb81201bc355f61…

MALICIOUS

RTF / .DOC

710.7 KB
MD5: 2ed4da2fd6fa4adb14bbc80738482f71 SHA-1: 63fc196e91eb76ac027edbe2a779ae270b79e46e SHA-256: 5eb81201bc355f61ea1af06f97d3cabfba4e602403d1f78c61750d7e3a80bcaa
80 Risk Score

Malware Insights

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

The sample is an RTF document containing an OLE object, which is a common technique for embedding malicious content. The heuristic 'SE_ENABLE_LURE' indicates the document instructs the user to enable editing, a typical lure to bypass security measures and execute embedded code. The presence of an OLE object and the lure suggest the document is designed to exploit vulnerabilities or trick the user into running a payload.

Heuristics 3

  • \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
  • 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 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000409ab.bin
d45291f9d2c9ecff4a4e266bba0cbc85afe42bf4c97d74f9a09d8fef6bfb4b3c
rtf-objdata-decoded RTF \objdata at offset 0x409AB 1915 bytes