Office (OLE) malware analysis — malicious · e76cb804ba74aa1e

MALICIOUS

Office (OLE)

22.5 KB Created: 1997-09-23 11:25:00 Authoring application: Microsoft Word for Windows 95 First seen: 2012-06-14

MD5: ee36062bc2bc52778fe8cbf5ee3d6519 SHA-1: 641d340490d1b3fbb3128cb260fe8eca94eef110 SHA-256: e76cb804ba74aa1ec16516a76d35b80f0b5cd45de89459f635fccacb1c22be11

200 Risk Score

Malware Insights

MITRE ATT&CK

T1059.005 Visual Basic

The file is a legacy Word document containing a WordBasic AUTOOPEN macro, indicated by the OLE_LEGACY_WORDBASIC_AUTOEXEC heuristic. This macro is designed to execute automatically upon opening, suggesting a malicious intent to run arbitrary code. The presence of embedded OLE findings and slack space anomalies further supports its suspicious nature.

Heuristics 5

ClamAV: Win.Trojan.Twno-10 critical CLAMAV_DETECTION

ClamAV detected this file as malware: Win.Trojan.Twno-10
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.
OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY

OLE file is 17,559 bytes but its declared streams total only 0 bytes — 17,559 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).
Legacy WordBasic auto-exec macro marker medium OLE_LEGACY_WORDBASIC_AUTOEXEC

OLE Word document contains a legacy WordBasic auto-execution marker such as AutoOpen, but no modern VBA project was recovered and no stronger macro-virus family marker was present. This is analyst-facing evidence for old Word macro execution surface, not a downloader or parser-CVE attribution by itself.
CFB header with no readable streams medium OLE_PARSE_EMPTY_STREAMS

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_off00001569.ole`	embedded-office	Embedded OLE/CFB Office body inside ole container at offset 0x1569	17559 bytes
SHA-256: `d0e581c650a33689a8d8be4517e14aa2ec1392f8189d4dd5fad7f4a11ddc720b`

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