Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 10d50a09310d58a5…

MALICIOUS

RTF / .DOC

11.4 KB First seen: 2022-10-03
MD5: 3b9b303091bd2ad953d52b4689aea888 SHA-1: c7c9d4d948f78c408dd7a387da8269dc33f27e04 SHA-256: 10d50a09310d58a5c545642cb554c0480af907ff610165151365146f56fd5642
140 Risk Score

Malware Insights

MITRE ATT&CK
T1204 Malicious Link T1204.002 Malicious Link: Malicious File T1566 Phishing T1566.001 Phishing: Spearphishing Attachment T1059.005 Command and Scripting Interpreter: Visual Basic

The sample is an RTF document containing an embedded OLE object, specifically targeting the Equation Editor vulnerability. The document body contains a lure instructing the user to 'Enable editing' to view the content, a common social engineering tactic. The presence of RTF_OBJDATA and RTF_OBJUPDATE heuristics further indicates the exploitation of OLE object vulnerabilities.

Heuristics 4

  • Split hex Equation Editor ProgID + OLE object critical RTF_EQUATION_EDITOR
    RTF embeds the Equation.3 ProgID as hex bytes near OLE object activation and splits the byte stream with whitespace or an ignorable RTF group. This is an Equation Editor OLE activation surface commonly used by CVE-2017-11882 / CVE-2018-0802 exploit documents.
  • \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_off00001264.bin
c4b48c2e12c70ea39a555b3ba31ad8d5cf9f9846e031c293d0502b00fd25e624
rtf-objdata-decoded RTF \objdata at offset 0x1264 1363 bytes