Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 42b70aba7f8a2fdf…

MALICIOUS

RTF / .DOC

23.8 KB First seen: 2023-05-18
MD5: 1e43ff2ce3d2429206465f2405d0e411 SHA-1: 0385ee924643ccda899693f527836a0e4dd2ec27 SHA-256: 42b70aba7f8a2fdf79437f771df8cd0a9ebabee932d440a6265fcf241b60c08d
100 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1204.002 Malicious File

The RTF document contains OLE object data and uses \objupdate to force OLE activation, indicating an attempt to exploit vulnerabilities. The presence of OLE10Native stream further supports this. While no specific document body content or scripts were extracted, the heuristics strongly suggest a malicious OLE object designed to execute code upon opening.

Heuristics 3

  • Ole10Native stream in RTF OLE object high CVE related RTF_OLE10NATIVE_STREAM
    RTF 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.
  • \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

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off0000162e.bin
39ab6ab469e6934d548aaddffe4feede2320ec0156fa228e77afac12bfa153d7
rtf-objdata-decoded RTF \objdata at offset 0x162E 3687 bytes