Win.Trojan.MDMA-4 — Office (OLE) / .DOC malware analysis

Static analysis result for SHA-256 7ed71c4a284643f7…

MALICIOUS

Office (OLE) / .DOC

26.0 KB Created: 1998-01-28 08:20:00 Authoring application: Microsoft Word 6.0
MD5: 4958581d1832dd2f84fde0df88d18217 SHA-1: af99a780f72dd9d44b6531646b524957ccbbfec6 SHA-256: 7ed71c4a284643f76fcf134080fd715691338963fecdf422cd864a1153c92e41
240 Risk Score

Malware Insights

Win.Trojan.MDMA-4 · confidence 90%

MITRE ATT&CK
T1203 Exploitation for Client Execution

The file is identified as malicious by ClamAV with the signature Win.Trojan.MDMA-4. Heuristics indicate an embedded Office document with suspicious static findings, including OLE slack anomalies and unreadable streams, suggesting an attempt to hide malicious content. The embedded artifact 'embedded_office_off0000108a.ole' is likely the malicious component.

Heuristics 5

  • Embedded Office document has suspicious static findings critical EMBEDDED_OFFICE_CHILD_STATIC_TRIAGE
    A CFB/OLE Office document was found inside another file type and its carved contents matched Office exploit or payload heuristics. This catches wrapped exploit documents where the top-level file routes to a PE, archive, or generic scanner instead of Office.
  • ClamAV: Win.Trojan.MDMA-4 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Win.Trojan.MDMA-4
  • ClamAV detection on extracted artifact critical EXTRACTED_FILE_CLAMAV
    ClamAV flagged at least one file extracted from inside this sample. Even when the wrapping document carries no AV detection of its own, a hit on the carved artifact is a strong indicator the sample is a delivery vehicle.
  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 26,624 bytes but its declared streams total only 10,220 bytes — 16,404 bytes (62%) live in unallocated sector slack. This is the canonical hiding place for pre-macro-era Office exploit payloads (XOR-encoded shellcode reached via a parser pointer-corruption bug in the document structure).
  • CFB header with no readable streams medium OLE_PARSE_EMPTY_STREAMS
    The file begins with a valid OLE2/CFB header but exposes no directory streams. A non-empty compound document with an unreadable directory is anomalous — it is seen with truncated/corrupt files and, more importantly, with content deliberately shifted off byte boundaries to defeat parsers while the host application still recovers the object.

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
embedded_office_off0000108a.ole
ef5a77b2472dcfd7c2765e54a25262babb53a3ba47971e3107cdc0829a040aa2
embedded-office Embedded OLE/CFB Office body inside ole container at offset 0x108A 22390 bytes
Detection
ClamAV: Win.Trojan.MDMA-4
Obfuscation or payload: unlikely