Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 9f3cb1ca2dd93a95…

MALICIOUS

RTF / .DOC

13.5 KB
MD5: 7379e1188815d7e39ab45b79abc3537c SHA-1: 4c382a0e11cb0abc3d269ec0ebc3a5b36526ee2b SHA-256: 9f3cb1ca2dd93a951cc7a77bad6fe68fb495a8af4a28e9b9df8c1e015686ec3f
100 Risk Score

Malware Insights

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

The RTF document contains OLE object data and is configured to automatically update these objects. This suggests an attempt to exploit OLE vulnerabilities or trick the user into activating embedded content. The heuristics RTF_OBJAUTLINK and RTF_OBJUPDATE strongly indicate that the document is designed to automatically execute embedded content upon opening, likely leading to the download or execution of a secondary payload. The specific nature of the payload cannot be determined from the provided evidence.

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_off00000d80.bin
4836063e9cd407407ed98547178df746a9cac96c46f06a61ed03308963d280da
rtf-objdata-decoded RTF \objdata at offset 0xD80 1734 bytes