Malicious RTF — malware analysis report

Static analysis result for SHA-256 8b018721d05a6bd5…

MALICIOUS

RTF

163.2 KB Authoring application: Msftedit 5.41.15.1507 First seen: 2015-10-02
MD5: d5a70a26485f4ba5ec1ec542b97c8a40 SHA-1: a87763811ec0f4172a35e9694b9ced15399fff87 SHA-256: 8b018721d05a6bd593533bf1193d8ada65553d0629411b5e8bef0cba0654af84
142 Risk Score

Malware Insights

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

The RTF document contains an embedded OLE object, identified as a package object, which in turn contains a PE executable in its objdata. The embedded URL suggests a command and control communication channel. The presence of a PE header within the objdata strongly indicates that the embedded object is a payload designed for execution.

Heuristics 5

  • 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
  • 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
  • Embedded URL info EMBEDDED_URL
    One or more URLs were extracted from the document. The URL itself is not a detection — see the per-URL labels for which channel (macro, JS, link annotation, document body, ...) reached each URL.
    URL http://%s:%i%s?mod=cmd&user=%s In RTF body

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off0000010e.bin rtf-objdata-decoded RTF \objdata at offset 0x10E 77583 bytes
SHA-256: ad9653db3b186f83342fe4924f93ac4398f1ca3adff48b7585093bdc27acdd22

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