Win.Trojan.Talon-5 Office (OLE) malware analysis — malicious · e2bd733eb3e76b8d

MALICIOUS

Office (OLE)

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

MD5: e527db564b08345323fce7d0796fdbd1 SHA-1: f4c51f930d80d844478edd007d867f6892c61f84 SHA-256: e2bd733eb3e76b8d3d60a8ee759972f2bfa274c926066316150d9ed0479f47aa

180 Risk Score

Malware Insights

Win.Trojan.Talon-5 · confidence 95%

MITRE ATT&CK

T1204.002 Malicious File T1059.005 Visual Basic

The file is identified as a legacy WordBasic macro-virus by heuristics, indicating an attempt to leverage old macro capabilities for malicious purposes. The critical heuristic 'EMBEDDED_OFFICE_CHILD_STATIC_TRIAGE' with a score of 60 further supports this, pointing to suspicious findings within an embedded Office object. ClamAV detection as 'Win.Trojan.Talon-5' confirms its malicious nature. The presence of legacy WordBasic markers suggests an attack pattern involving user interaction to trigger the embedded malicious code.

Heuristics 4

ClamAV: Win.Trojan.Talon-5 critical CLAMAV_DETECTION

ClamAV detected this file as malware: Win.Trojan.Talon-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.
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	14080 bytes
SHA-256: `552326aa25af3d854eefbe53d33596dc020c8559ddb43ea355eeb5d362b7294e`

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