Win.Trojan.Olympic-3 Office (OLE) malware analysis — malicious · fc294f3f543edad0

MALICIOUS

Office (OLE)

24.5 KB Created: 1996-08-01 11:54:00 Authoring application: Microsoft Word 6.0 First seen: 2012-06-14

MD5: a0154401e6935e5334928a99a0a424aa SHA-1: e2e9256a80637411ffab1e556350b4bbda9433cb SHA-256: fc294f3f543edad0fbaf03232c0e8d1f8b8111188626e8fda9ef4f048af82d85

200 Risk Score

Malware Insights

Win.Trojan.Olympic-3 · confidence 95%

MITRE ATT&CK

T1059.005 Visual Basic

The file is a legacy Word document containing a WordBasic AUTOOPEN macro, which is a known technique for executing malicious code automatically when the document is opened. ClamAV identifies this as Win.Trojan.Olympic-3. The embedded OLE structure also shows anomalies suggesting an attempt to evade parsing.

Heuristics 5

ClamAV: Win.Trojan.Olympic-3 critical CLAMAV_DETECTION

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

OLE file is 20,761 bytes but its declared streams total only 0 bytes — 20,761 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_off000010e7.ole`	embedded-office	Embedded OLE/CFB Office body inside ole container at offset 0x10E7	20761 bytes
SHA-256: `060746e0545a508d10c41a6f7d8b275bec67f0f26aaaab3d1226027ffed8fdeb`

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