Malicious RTF — malware analysis report

Static analysis result for SHA-256 fa63a1c6e692c90a…

MALICIOUS

RTF

500.8 KB Created: 2017-12-11 03:51:00 First seen: 2018-08-14
MD5: 806819b169dfcaa962d7f5c32c03a0b3 SHA-1: e7d0b90f4fec1ef5d1476f3f950d5fce833c664c SHA-256: fa63a1c6e692c90a90dba6d8c566b2ed0a094a82e58f6f65cbdca5b8aa0d8052
162 Risk Score

Malware Insights

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

The RTF document contains multiple embedded OLE objects and triggers the CVE-2017-8759 exploit, which is known for allowing arbitrary code execution. This exploit is typically delivered via spearphishing attachments, suggesting a malicious intent to compromise the user's system.

Heuristics 5

  • CVE-2017-8759 — MSXML SAX OLE activation critical CVE likely CVE_2017_8759
    RTF contains a hex-encoded OLE1 object for Msxml2.SAXXMLReader.6.0 followed by an embedded OLE compound document, and the document requests OLE activation. This matches the RTF staging shape used for CVE-2017-8759 SOAP/WSDL parser code injection.
  • ClamAV: Doc.Exploit.DDEautoexec-6346603-1 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Doc.Exploit.DDEautoexec-6346603-1
  • OLE object data medium RTF_OBJDATA
    RTF contains 10 \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://schemas.microsoft.com/office/word/2003/wordml In RTF body

Extracted artifacts 8

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000035b1.bin rtf-objdata-decoded RTF \objdata at offset 0x35B1 19505 bytes
SHA-256: a36b1413452dc0714e1055bd6d2acda0332d393cd7348ebddb73128564c6ed5c
objdata_01_off0000eacd.bin rtf-objdata-decoded RTF \objdata at offset 0xEACD 19505 bytes
SHA-256: dffd8e51d7e61ced440dd288a456d7568819197591c7968ef6341be2000f8a73
objdata_02_off00019fe9.bin rtf-objdata-decoded RTF \objdata at offset 0x19FE9 19505 bytes
SHA-256: fcfd9cadf95abc47871fe7ab80e5417119200189f2bbdcc0073f5386ecd12064
objdata_03_off00025505.bin rtf-objdata-decoded RTF \objdata at offset 0x25505 19505 bytes
SHA-256: e2c37758cec562ccd5a1f4e7c813166fa3767b8f1cbae00bae6ad9495ce1c96e
objdata_04_off00030a21.bin rtf-objdata-decoded RTF \objdata at offset 0x30A21 19505 bytes
SHA-256: eb43228f1652adbe372ec0da28682b3e6536ffba761209dcc838dd6dce5a0ba3
objdata_05_off0003bf3d.bin rtf-objdata-decoded RTF \objdata at offset 0x3BF3D 19505 bytes
SHA-256: 09bd54640c47c67e02cf2864049e6be37c978584656ab789f0c8c6c8b8446a6d
objdata_06_off00047459.bin rtf-objdata-decoded RTF \objdata at offset 0x47459 19505 bytes
SHA-256: cd6e92465c5a0a9e1ed5aa34129ac917ad7906a7638fc8728e80210393179d23
objdata_07_off00052976.bin rtf-objdata-decoded RTF \objdata at offset 0x52976 19505 bytes
SHA-256: c4004cff9e727ac7adca56bd9234e1bc3d93ea11bed39a109a28577501f8cbdf

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