Malicious RTF — malware analysis report

Static analysis result for SHA-256 be072be325a70094…

MALICIOUS

RTF

21.6 KB
MD5: 6dbc6acca14919b37309c80b6ed82c07 SHA-1: 327e1c2ed05b2ed85d30d25075ccbfe181bbcf0f SHA-256: be072be325a7009480aaa52fbda5796e9fcaf8909d5da001836b48a196c00ee8
120 Risk Score

Malware Insights

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

The RTF file contains embedded OLE objects that are forced to activate via \objupdate. This indicates a technique to execute embedded code or launch an embedded file. The presence of \objdata and \OLE10NATIVE_STREAM further supports the malicious nature of the embedded object. While no specific script was extracted, the heuristics strongly suggest the OLE object is designed to execute a secondary payload, likely leading to further system compromise.

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_off00000b24.bin
31730433f50c4cc197ebb300642ce19dd0720f6f74e966200c6e17ce39e54607
rtf-objdata-decoded RTF \objdata at offset 0xB24 4180 bytes