Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 8573e361985adafe…

MALICIOUS

RTF / .DOC

99.3 KB
MD5: 20d27507cb76f55e73b9531035e2b266 SHA-1: 0864ca9061aad1a5a328bf99ac858c88dfd62e9e SHA-256: 8573e361985adafebf286a7115b0ff783f3432defcb415d45df2c46f04104cfe
100 Risk Score

Malware Insights

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

The sample is an RTF document that contains OLE object data and is configured to automatically update and activate these objects. This indicates a likely attempt to exploit OLE vulnerabilities to execute embedded malicious code. No specific document body text or scripts were extracted, limiting the ability to determine the exact payload or further infection chain. The heuristics strongly suggest a malicious OLE object execution.

Heuristics 3

  • Automatically linked OLE object high RTF_OBJAUTLINK
    RTF contains \objautlink — an automatically linked OLE object surface that can be updated or activated when Word opens the document.
  • \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 2 \objdata section(s) — embedded OLE objects

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00000a9a.bin
eeedb44755c0b1c30aafd8bb2f0e84e9e236be47762d0287cdb5bd169d474c2b
rtf-objdata-decoded RTF \objdata at offset 0xA9A 1854 bytes