Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 cd6eab2fafb7b32e…

MALICIOUS

RTF / .DOC

351.3 KB
MD5: 5662716add21395fd1208f1963f34e9e SHA-1: 9dcce317afe9e1475e12d5a1f45b4a48c6d9e6b4 SHA-256: cd6eab2fafb7b32ebb1b9da555ba9a9a2276df141349a60598cd6d3f93180342
174 Risk Score

Malware Insights

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

The RTF document contains an OLE object that is configured to update automatically upon opening. This technique is commonly used to deliver malicious payloads. While the specific payload and its ultimate destination are not detailed in the provided evidence, the presence of the OLE object and the auto-update trigger strongly suggest a malicious intent to execute code. The file's SHA256 hash is included as a primary indicator.

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_off00001b03.bin
ddd2086c915b6263b570c8045a660efcaeac2e77475f55bbd1d291ec29d45e3b
rtf-objdata-decoded RTF \objdata at offset 0x1B03 64060 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 7.93, consistent with packed or encrypted content.