Office (OLE) malware analysis — malicious · d7fe1c6e7fa0c9ff

MALICIOUS

Office (OLE)

20.5 KB Created: 1997-03-23 06:12:00 Authoring application: Microsoft Word for Windows 95 First seen: 2012-06-14

MD5: 87ac41bfc3c6073885d7a3a92747ef7d SHA-1: 08d4babde808ff5af7d3f7d34875460e5dde224d SHA-256: d7fe1c6e7fa0c9ff9939585c27fccb2d7f61b8d1f0464d20126a36e332d81720

180 Risk Score

Malware Insights

MITRE ATT&CK

T1059.005 Visual Basic

The file exhibits characteristics of a legacy WordBasic macro virus, specifically identified by the 'ToolsMacro' marker. The presence of embedded Office findings and the ClamAV detection as 'Win.Trojan.Dark-6' strongly indicate malicious intent. The document body, while containing unusual text, references 'DarkSide1' and 'Laboratorio de Hackers-97', further supporting a malware classification.

Heuristics 4

ClamAV: Win.Trojan.Dark-6 critical CLAMAV_DETECTION

ClamAV detected this file as malware: Win.Trojan.Dark-6
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_off000016d5.ole`	embedded-office	Embedded OLE/CFB Office body inside ole container at offset 0x16D5	15147 bytes
SHA-256: `86afe4bdb15bd8c592b71cca7a3171d78e4ef72573b8e4c68b5f35809fab2f4e`

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