Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 d9043481ac860270…

MALICIOUS

RTF / .DOC

223.1 KB
MD5: ea1a74f2b093e3aca5137f2399b08fe1 SHA-1: 5c1b5844a2cb4ae365438da10fef6e85a79fc232 SHA-256: d9043481ac860270c7b3884fd58107184ab08605da067ed42daff1ab1ac5eba7
120 Risk Score

Malware Insights

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

The sample is an RTF document containing embedded OLE objects, with heuristics indicating that \objupdate forces OLE activation. This suggests the document is designed to exploit vulnerabilities or trick the user into executing embedded content. No document body or script content was available for further analysis, limiting the ability to determine the exact payload or delivery mechanism. The high entropy of the decoded OLE object suggests it may be packed or encrypted.

Heuristics 4

  • 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 2 \objdata section(s) — embedded OLE objects
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off0000128f.bin
439e16d5035baa23c12162c47077c621ea729640d4d6e58ecccb88965115df41
rtf-objdata-decoded RTF \objdata at offset 0x128F 4155 bytes