Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 454b8a1236e5c819…

MALICIOUS

RTF / .DOC

447.5 KB
MD5: 398dd67cef5047e52c2e4a9c558b21dc SHA-1: 1ce7af923e02a02e3af31be8099a5eaa9d267310 SHA-256: 454b8a1236e5c819a5eb73785d04de86f951ee7dc99d00698a60f2b7abdad407
174 Risk Score

Malware Insights

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

The RTF document contains OLE object data and uses an \objupdate directive, indicating an attempt to exploit OLE object handling vulnerabilities. This suggests a malicious document designed to execute code upon opening. The specific exploit and payload are not immediately clear from the static analysis, but the technique is indicative of a downloader or initial access exploit.

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_off00001a4d.bin
ed319422bbaa102a08b7fe35acb517b11ad182d790c5858bc55339b1874e0cff
rtf-objdata-decoded RTF \objdata at offset 0x1A4D 129065 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 7.97, consistent with packed or encrypted content.