Malicious RTF — malware analysis report

Static analysis result for SHA-256 c38d511f76083fd6…

MALICIOUS

RTF

82.8 KB First seen: 2025-08-13
MD5: 50af5260770fe6a4e00a31d039b95f64 SHA-1: 80923be74ce7cb2a015ce5dafe537afae01d4e25 SHA-256: c38d511f76083fd6f4fc0afe6b700dc0a1998b612f78f9fc85d2aa6e811f3001
100 Risk Score

Malware Insights

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

The RTF file contains OLE object data and uses \objupdate to force activation, indicating an attempt to exploit OLE vulnerabilities. The presence of \objupdate and Ole10Native stream suggests the embedded OLE object is designed to execute malicious code upon opening. No document body or script content was available for further analysis, limiting the ability to determine the specific payload or delivery mechanism.

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_off00002063.bin
4d173a0935900e58ba5cf1b83f9fbcbc7efbd7da1ad89201e75ba82e922f4f29
rtf-objdata-decoded RTF \objdata at offset 0x2063 4201 bytes