Win.Trojan.Angel-3 Office (OLE) malware analysis — malicious · 6fef9525ebcf4827

MALICIOUS

Office (OLE)

32.5 KB Created: 1993-09-28 15:08:00 Authoring application: Microsoft Word for Windows 95 First seen: 2015-09-17

MD5: 2ff96bbb2337284597e55c45d3a73250 SHA-1: d26aef273f8ec70f27ac9af5b04bb64b12b30bda SHA-256: 6fef9525ebcf4827181b2aad0c5009808ba0824def28fd24afd30593e3b2176d

260 Risk Score

Malware Insights

Win.Trojan.Angel-3 · confidence 95%

MITRE ATT&CK

T1059.005 Visual Basic

The file exhibits characteristics of a legacy macro-virus, specifically triggering OLE-related heuristics indicating a manipulated or corrupt structure designed to hide malicious content. ClamAV identifies it as Win.Trojan.Angel-3. The presence of legacy WordBasic macro markers suggests an attempt to execute embedded code, likely for malicious purposes.

Heuristics 6

ClamAV: Win.Trojan.Angel-3 critical CLAMAV_DETECTION

ClamAV detected this file as malware: Win.Trojan.Angel-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.
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 24,833 bytes but its declared streams total only 0 bytes — 24,833 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).
Suspicious extracted artifact high EXTRACTED_FILE_STATIC_TRIAGE

One or more files extracted from inside this sample matched static suspicious-content checks such as script obfuscation, encoded payload blobs, packed data, or execution/download terms.
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	24833 bytes
SHA-256: `4ca953aa86b5b6dde78156c84f55be036ff6dda400388fca2bb54d1471c95841`
Detection ClamAV: No threats found Obfuscation or payload: likely Carved macro source contains an auto-exec entry point and execution/download terms.

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