Doc.Trojan.Wazzu-6 — Office (OLE) malware analysis

Static analysis result for SHA-256 0fafdb4ce9b984b3…

MALICIOUS

Office (OLE)

13.0 KB Created: 1601-01-01 00:00:00 Authoring application: Microsoft Word 6.0 First seen: 2012-06-14
MD5: 30e9ca0584588b5f5416c97e2391e1db SHA-1: e28df6e8221f6c8d0f8dd6131109759a858155e3 SHA-256: 0fafdb4ce9b984b3ef63a60adc35e9295b9fffdeafa196210eb89489c8736b40
240 Risk Score

Malware Insights

Doc.Trojan.Wazzu-6 · confidence 95%

MITRE ATT&CK
T1059.005 Visual Basic

The file exhibits legacy WordBasic macro virus markers and embedded OLE objects, strongly indicating malicious intent. ClamAV signatures confirm this, identifying it as Doc.Trojan.Wazzu-6. The presence of 'fileMacro$', 'globMacro$', and 'autoOpendRi' within the document body suggests the execution of embedded macros, likely to perform malicious actions.

Heuristics 4

  • ClamAV: Doc.Trojan.Wazzu-6 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Doc.Trojan.Wazzu-6
  • 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_off00001c80.ole embedded-office Embedded OLE/CFB Office body inside ole container at offset 0x1C80 6016 bytes
SHA-256: 973a09d3cb4348dc3ce60e3af0aea8f711217a5a28cdbfacf166edd0c940e3c3
Detection
ClamAV: Doc.Trojan.Wazzu-6
Obfuscation or payload: unlikely