Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 2b596be066a85c5b…

MALICIOUS

RTF / .DOC

354.0 KB
MD5: 7e615588a8f136d9e0ad12b9c94e1dc0 SHA-1: 22c9c48398442d5c8d3851e7e9c5e4020946704a SHA-256: 2b596be066a85c5b338f606108824865ffb1c1d8400d488d45ba813da05ff02e
174 Risk Score

Malware Insights

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

The RTF file contains OLE object data and uses an \objupdate command, indicating an attempt to embed and activate an object. This is a common technique for delivering malicious payloads. While no specific family is identified, the method suggests a downloader or exploit delivery mechanism. The embedded OLE object is the primary IOC.

Heuristics 3

  • \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
  • Suspicious extracted artifact info EXTRACTED_FILE_STATIC_TRIAGE
    One or more files extracted from inside this sample matched static suspicious-content checks such as script obfuscation, encoded payload blobs, packed data, or execution/download terms.

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00001d52.bin
b627c8e8c289ffa3d64adeca63bd094effeebecc794e2ecd6640c51b5417dafc
rtf-objdata-decoded RTF \objdata at offset 0x1D52 64570 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 7.92, consistent with packed or encrypted content.