Win.Trojan.Vampire-11 — Office (OLE) malware analysis

Static analysis result for SHA-256 af26865c2ea31da3…

MALICIOUS

Office (OLE)

39.5 KB Created: 1997-05-15 13:24:00 Authoring application: Microsoft Word for Windows 95 First seen: 2012-06-14
MD5: 06b3ab14cad534f001294b934a86e8f4 SHA-1: 9f647769e3544569d96774b6cd39060b217fe58a SHA-256: af26865c2ea31da383c023c79bf585d21824969817992e51c97a92662f03f73d
220 Risk Score

Malware Insights

Win.Trojan.Vampire-11 · confidence 95%

MITRE ATT&CK
T1059.005 Visual Basic

The file exhibits characteristics of a legacy WordBasic macro virus, specifically identified by the 'TOOLSMACRO' marker and ClamAV's detection of 'Win.Trojan.Vampire-11'. The embedded OLE structures also show anomalies and empty streams, suggesting an attempt to obfuscate malicious content. These findings strongly indicate the document is designed to execute a malicious payload via its macros.

Heuristics 5

  • ClamAV: Win.Trojan.Vampire-11 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Win.Trojan.Vampire-11
  • 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 19,656 bytes but its declared streams total only 0 bytes — 19,656 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.

FilenameKindSourceSize
embedded_office_off00005138.ole embedded-office Embedded OLE/CFB Office body inside ole container at offset 0x5138 19656 bytes
SHA-256: 72ee84645081db5eb5b03d389575ce05eacf35693048fc2b7a7b8f76f4941f0d

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