RTF malware analysis — malicious · 4b9eacc3922d128d

MALICIOUS

RTF

3.69 MB Authoring application: Msftedit 5.41.15.1515

MD5: ab9115522131c4de4447b61476ab09f7 SHA-1: 1a1f64474d99de00b40eed084b6dac2329299159 SHA-256: 4b9eacc3922d128d205fddd2be2f4e60e61f8ad01943f0d15412aadc7a31fbda

182 Risk Score

Malware Insights

MITRE ATT&CK

T1559.001 Component Object Model Hijacking T1105 Ingress Tool Transfer

The RTF file contains a large amount of hex-encoded data within an OLE object, which includes a PE header. This strongly indicates that the RTF is acting as a container to deliver a malicious executable payload. The presence of OLE object data and a PE header within the hex data points to a dropper functionality.

Heuristics 6

PE header (with DOS stub) in hex data critical RTF_MZ_HEX

Hex-encoded PE (MZ + DOS stub) found inside RTF — likely an embedded executable payload
Package object class high RTF_OBJCLASS_PACKAGE

OLE Package object — can wrap arbitrary files
Large hex data blocks in OLE object high RTF_EXCESSIVE_HEX

RTF contains ~3575KB of hex-encoded data inside \objdata sections — may hide a payload
OLE object data medium RTF_OBJDATA

RTF contains 1 \objdata section(s) — embedded OLE objects
Embedded OLE object medium RTF_OBJEMB

RTF contains \objemb — embedded OLE object
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.

Filename	Kind	Source	Size
`objdata_00_off000000d3.bin` `f4bebf9008bf6fe3b3a82bb8bd5976f6e54fb546432526b40568c90bc7594b59`	rtf-objdata-decoded	RTF \objdata at offset 0xD3	1743184 bytes
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact entropy is 7.76, consistent with packed or encrypted content.

Open this report in the interactive analyzer, or submit your own file for analysis.