Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 bb54f040bace0686…

MALICIOUS

Office (OLE)

40.5 KB Created: 1601-01-01 00:00:00 Authoring application: Microsoft Word 6.0 First seen: 2012-06-14
MD5: f40390ce71dadc62a28a5b26eec4e5ae SHA-1: 4fd266996489762e9de7cff9650ee83961a7d299 SHA-256: bb54f040bace06860137023a39747c13a078ab7be490eaf1e1c9843494286582
220 Risk Score

Malware Insights

MITRE ATT&CK
T1059.005 Visual Basic

The presence of legacy WordBasic macro virus markers, specifically 'ToolsMacro', along with anomalous OLE structure and empty streams, strongly suggests a malicious macro-based document. The embedded artifact 'CHICKEN.DOC' and the 'ToolsMacro' heuristic point towards the execution of embedded macro code.

Heuristics 5

  • ClamAV: Win.Tool.WM-5 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Win.Tool.WM-5
  • 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 26,059 bytes but its declared streams total only 0 bytes — 26,059 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_off00003c35.ole embedded-office Embedded OLE/CFB Office body inside ole container at offset 0x3C35 26059 bytes
SHA-256: 9ea8acf09e53618667950f9e89f3474663e60ca8e829d0d40ac547809bcf1da1

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