Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 192bd09f84bb8730…

MALICIOUS

RTF / .DOC

446.5 KB
MD5: 8f55ac02d7b5fc4f35df81c5d43b0947 SHA-1: 0d278f1f034dd7e35f1f9ef02f7382b6047abf1e SHA-256: 192bd09f84bb87300ee9c86aefb2f47e4c27ae9709a5a44329024b2dd2f273f0
62 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1203 Exploitation for Client Execution

The RTF document contains OLE object data, indicated by the RTF_OBJDATA heuristic. The RTF_OBJUPDATE heuristic suggests that this embedded object is intended to be activated, likely to execute a payload. The presence of a suspicious extracted artifact, objdata_00_off00001c95.bin, further supports this. While no specific script was extracted, the overall structure points towards an attempt to exploit the OLE object mechanism for initial execution, commonly seen in spearphishing attachments.

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_off00001c95.bin
b0da9f36ed0338084a13aa4b9115fb4e8218e1fd16e449b93345afc079995897
rtf-objdata-decoded RTF \objdata at offset 0x1C95 128559 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 7.98, consistent with packed or encrypted content.