Win.Trojan.Lucifer-5 — Office (OLE) malware analysis

Static analysis result for SHA-256 5cd5d058b42579f8…

MALICIOUS

Office (OLE)

35.5 KB Created: 1601-01-01 00:00:00 Authoring application: Microsoft Word 6.0 First seen: 2012-06-14
MD5: 6c6b7df5c5c9b0bf6637780696be01cd SHA-1: 6597f3325a0e3f986b66c469d1a2c343d80127ec SHA-256: 5cd5d058b42579f88d6407289de0e0689a8b7606375ef30c0b54a206f3a7a830
200 Risk Score

Malware Insights

Win.Trojan.Lucifer-5 · confidence 95%

MITRE ATT&CK
T1059.005 Visual Basic

The file is identified as a legacy Word document containing an AutoOpen macro, a common indicator for older malware execution. ClamAV detection confirms it as Win.Trojan.Lucifer-5. The presence of the AutoOpen macro suggests an attempt to automatically run malicious code when the document is opened, likely leading to further infection or payload delivery.

Heuristics 5

  • ClamAV: Win.Trojan.Lucifer-5 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Win.Trojan.Lucifer-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.
  • OLE document has large unaccounted-for region high OLE_SLACK_ANOMALY
    OLE file is 24,679 bytes but its declared streams total only 0 bytes — 24,679 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_off00002d99.ole embedded-office Embedded OLE/CFB Office body inside ole container at offset 0x2D99 24679 bytes
SHA-256: 0d6dd13fe7b83fa78b748c83e00e2e31f919f248fa3209072af0e9666276bad8

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