Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 ccf0e88be2c57504…

MALICIOUS

RTF / .DOC

162.7 KB
MD5: 3a75522944894bbc08ed889a5df9a094 SHA-1: 02558d66e63ea9c7a18d0d1e196074caf9413af3 SHA-256: ccf0e88be2c575045ab51dcb89d2a62601d2ee91a620601bdf3e297240cf2137
129 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 an \objupdate directive, indicating an attempt to embed and activate an object. This is a common technique for delivering malicious payloads. While no specific family is identifiable, the method suggests a downloader or exploit delivery mechanism. The document body is heavily obfuscated and does not provide clear intent.

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_off000018b1.bin
13324156fdeea3350e34fba3294bc43b514fb425b9feee9634b2f41a4a4a0b51
rtf-objdata-decoded RTF \objdata at offset 0x18B1 64061 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 7.92, consistent with packed or encrypted content.