Win.Trojan.Demon — Office (OLE) malware analysis

Static analysis result for SHA-256 5232af2934aaef5d…

MALICIOUS

Office (OLE)

42.0 KB Created: 1997-12-17 15:43:00 Authoring application: Microsoft Word for Windows 95 First seen: 2012-06-14
MD5: a37557adb118a2b933014b577d6fb640 SHA-1: e5826e6c56a791ad3ec6bb5fbeb334336ce90ae1 SHA-256: 5232af2934aaef5dc5ace41014c4531a56c20b6eae8d22cdd3f299a0672627d9
260 Risk Score

Malware Insights

Win.Trojan.Demon · confidence 95%

MITRE ATT&CK
T1059.005 Visual Basic

The file is identified as malicious by ClamAV with multiple detections, including Win.Trojan.Demon-9 and Win.Trojan.Demon-7. A critical heuristic indicates the presence of a legacy WordBasic AutoOpen macro, a common technique for executing malicious payloads. The embedded OLE document also exhibits suspicious static findings and slack space anomalies, suggesting deliberate obfuscation.

Heuristics 5

  • ClamAV: Win.Trojan.Demon-9 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Win.Trojan.Demon-9
  • 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 39,378 bytes but its declared streams total only 0 bytes — 39,378 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.

FilenameKindSourceSize
embedded_office_off00000e2e.ole embedded-office Embedded OLE/CFB Office body inside ole container at offset 0xE2E 39378 bytes
SHA-256: 57d0f046016e7c2533cdbed42a851c4bde3c02786a51d6312dbf3e537322bc2e
Detection
ClamAV: Win.Trojan.Demon-7
Obfuscation or payload: unlikely

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