Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 834035490a4614ce…

MALICIOUS

Office (OLE)

30.0 KB Created: 1997-01-15 16:05:00 Authoring application: Microsoft Word 6.0 First seen: 2017-02-23
MD5: f1b5817c35fa1ed744b5b2180b8ef141 SHA-1: e97fde0019c9222b8d8ebe950622b94beaa3b8ab SHA-256: 834035490a4614cef0318834a261f47455721c0ce80b3fdc5157ce6091bddc03
140 Risk Score

Malware Insights

MITRE ATT&CK
T1059.005 Visual Basic

The file exhibits characteristics of a legacy WordBasic macro-virus, indicated by the 'fileMacro$' marker. The presence of a large slack space anomaly in the OLE structure further suggests potential obfuscation or malicious intent. ClamAV detection as 'Doc.Trojan.Wazzu-6' confirms its malicious nature, likely involving the execution of embedded macro code.

Heuristics 3

  • ClamAV: Doc.Trojan.Wazzu-6 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Doc.Trojan.Wazzu-6
  • 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
    OLE file is 30,720 bytes but its declared streams total only 12,706 bytes — 18,014 bytes (59%) 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).

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