MALICIOUS
220
Risk Score
Malware Insights
MITRE ATT&CK
T1059.005 Visual Basic
The sample is identified as malicious by ClamAV with the signature Win.Trojan.MDMA-4. Static analysis detected a legacy WordBasic AutoClose macro, indicating an attempt to execute code upon document closure. The embedded artifact also shows suspicious findings related to OLE parsing, further supporting malicious intent.
Heuristics 4
-
ClamAV: Win.Trojan.MDMA-4 critical CLAMAV_DETECTIONClamAV detected this file as malware: Win.Trojan.MDMA-4
-
Embedded Office document has suspicious static findings critical EMBEDDED_OFFICE_CHILD_STATIC_TRIAGEA 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.
-
Legacy WordBasic auto-exec macro marker medium OLE_LEGACY_WORDBASIC_AUTOEXECOLE Word document contains a legacy WordBasic auto-execution marker such as AutoOpen, but no modern VBA project was recovered and no stronger macro-virus family marker was present. This is analyst-facing evidence for old Word macro execution surface, not a downloader or parser-CVE attribution by itself.
-
CFB header with no readable streams medium OLE_PARSE_EMPTY_STREAMSThe 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.
| Filename | Kind | Source | Size |
|---|---|---|---|
embedded_office_off0000227b.ole |
embedded-office | Embedded OLE/CFB Office body inside ole container at offset 0x227B | 5509 bytes |
SHA-256: b1bfe2c43f81f5477e0101fa5067eafba3288df95f8e3a799c9e00f1b81e5cb4 |
|||
|
Detection
ClamAV:
Win.Trojan.MDMA-4
Obfuscation or payload:
unlikely
|
|||
Open this report in the interactive analyzer, or submit your own file for analysis.