Win.Trojan.Vampire-12 Office (OLE) malware analysis — malicious · 441db13833d91410

MALICIOUS

Office (OLE)

24.0 KB Created: 1997-03-18 21:29:00 Authoring application: Microsoft Word for Windows 95 First seen: 2012-06-14

MD5: 07c447f160e0b7606393488807ab9132 SHA-1: d220eab305819245a55463b51b336728fbd87867 SHA-256: 441db13833d9141079598955483aa64d7b43768a65376f1782e3c059bc0c7543

280 Risk Score

Malware Insights

Win.Trojan.Vampire-12 · confidence 95%

MITRE ATT&CK

T1059.005 Visual Basic

The file exhibits critical heuristic firings indicating it is a legacy WordBasic macro-virus, specifically identified by ClamAV as Win.Trojan.Vampire-12. The presence of 'TOOLSMACRO' and other macro-related strings, along with embedded OLE findings, strongly suggests the document is intended to execute malicious macros. The embedded artifact and associated file paths point to the potential execution of this malware.

Heuristics 5

ClamAV: Win.Trojan.Vampire-12 critical CLAMAV_DETECTION

ClamAV detected this file as malware: Win.Trojan.Vampire-12
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.
Legacy WordBasic macro-virus markers high OLE_LEGACY_WORDBASIC_MACRO_VIRUS

OLE Word document contains legacy WordBasic auto-execution macro markers such as AutoOpen plus ToolsMacro/MacroFile/fileMacro/globMacro or named historical macro-virus strings. These old Word 6/95 macro forms are not exposed as a modern VBA project, so normal VBA source extraction can miss them.
OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY

This finding applies to a carved embedded Office document found at a nonzero offset inside the submitted file, not directly to the top-level document. OLE file is 20,241 bytes but its declared streams total only 0 bytes — 20,241 bytes (100%) 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

This finding applies to a carved embedded Office document found at a nonzero offset inside the submitted file, not directly to the top-level document. 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.

Filename	Kind	Source	Size
`embedded_office_off000010ef.ole`	embedded-office	Embedded OLE/CFB Office body inside ole container at offset 0x10EF	20241 bytes
SHA-256: `706fc35244fb92541b15bb8a1395a661cffc7238c390afc051581a38a7686a6d`
Detection ClamAV: Win.Trojan.Vampire-12 Obfuscation or payload: unlikely

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