Office (OLE) malware analysis — malicious · 970093aebb7e8e86

MALICIOUS

Office (OLE)

20.5 KB Created: 1993-09-28 16:08:00 Authoring application: Microsoft Word for Windows 95 First seen: 2012-06-14

MD5: 8a41e53e4e8667d06f924ff66b402389 SHA-1: d724b05af1fe01ec311cddd5a51b51c082c08652 SHA-256: 970093aebb7e8e868cccb6072002aa518234bd2516ae2f0f6494b60c5182f1d4

120 Risk Score

Malware Insights

MITRE ATT&CK

T1059.005 Visual Basic

The sample exhibits characteristics of legacy malware, specifically triggering heuristics related to WordBasic macro viruses and suspicious embedded Office document structures. The presence of 'ToolsMacro' and 'OLE_LEGACY_WORDBASIC_MACRO_VIRUS' strongly indicates the use of older macro techniques for malicious purposes. The embedded Office document findings, including 'OLE_PARSE_EMPTY_STREAMS' and 'OLE_FAT_CHAIN_LOOP', suggest a malformed or intentionally obfuscated structure designed to evade detection or execute embedded code.

Heuristics 3

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.

Filename	Kind	Source	Size
`embedded_office_off00002100.ole`	embedded-office	Embedded OLE/CFB Office body inside ole container at offset 0x2100	12544 bytes
SHA-256: `6d30af7dc81fd29fa3e6fe6254726950773f4fb1d44d0610c9882e80bdf9b84c`

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