Win.Trojan.Wompie-1 — Office (OLE) malware analysis

Static analysis result for SHA-256 a342a2a9640ad0b2…

MALICIOUS

Office (OLE)

15.5 KB Created: 1997-08-21 07:15:00 Authoring application: Microsoft Word 6.0 First seen: 2012-06-14
MD5: 03b982b4a35101c4397a0ea7aa412f51 SHA-1: 0365fcc240a5c33f82d969568bd23521a056b33d SHA-256: a342a2a9640ad0b21f91b3340906a2b566bb8c56b66c86eba49bd70415a29019
240 Risk Score

Malware Insights

Win.Trojan.Wompie-1 · confidence 95%

MITRE ATT&CK
T1059.005 Visual Basic

The sample exhibits critical heuristics indicating it is a legacy WordBasic macro-virus, specifically identified by ClamAV as Win.Trojan.Wompie-1. The document body explicitly describes the Wompie macro virus, its components, and its anti-debug and data-wiping capabilities. The presence of 'ToolsMacro' and various macro names like 'AutoOpen' and 'Wompie' further supports the macro-based attack vector.

Heuristics 4

  • ClamAV: Win.Trojan.Wompie-1 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Win.Trojan.Wompie-1
  • 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.
  • 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_off00001440.ole embedded-office Embedded OLE/CFB Office body inside ole container at offset 0x1440 10688 bytes
SHA-256: 0365fc8ab1cf79d7102ee9a8984fa05b2c03ed4cd5e7a751450ce8375f94e237
Detection
ClamAV: Win.Trojan.Wompie-1
Obfuscation or payload: unlikely