MALICIOUS
220
Risk Score
Malware Insights
MITRE ATT&CK
T1059.005 Visual Basic
The file is identified as a legacy Word document containing a WordBasic macro with an AutoClose event, a known indicator of malicious activity. Heuristics indicate the presence of a macro lure, instructing the user to enable content, and a suspicious OLE structure suggesting deliberate obfuscation. The ClamAV detection name 'Win.Trojan.GoodNight-2' strongly suggests the malware family and its likely function as a trojan.
Heuristics 6
-
ClamAV: Win.Trojan.GoodNight-2 critical CLAMAV_DETECTIONClamAV detected this file as malware: Win.Trojan.GoodNight-2
-
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.
-
OLE document has large unaccounted-for region high OLE_SLACK_ANOMALYOLE file is 35,328 bytes but its declared streams total only 17,705 bytes — 17,623 bytes (50%) 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).
-
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.
-
Macro/content-enable lure medium SE_ENABLE_LUREDocument instructs the user to enable macros or editing — a common technique used by malware droppers to bypass Office macro security settings
-
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_off00001417.ole |
embedded-office | Embedded OLE/CFB Office body inside ole container at offset 0x1417 | 30185 bytes |
SHA-256: 10f3bb57b37898bb867e08e15331eb45a3b4635f8dccd0b967dbde41fe65d029 |
|||
Open this report in the interactive analyzer, or submit your own file for analysis.