Win.Trojan.Mark-1 — Office (OLE) malware analysis

Static analysis result for SHA-256 290b9dca56297474…

MALICIOUS

Office (OLE)

45.0 KB Created: 1997-05-02 16:18:00 Authoring application: Microsoft Word 6.0 First seen: 2012-06-14
MD5: 6f471bb05927070226dc4da099a5d1d3 SHA-1: c9ea4dd1904c9fbb2400aa2aa670b7f0e770bca7 SHA-256: 290b9dca562974741708efb252549dc3c869e7a8f13e5da938b2b9f75fa668fb
220 Risk Score

Malware Insights

Win.Trojan.Mark-1 · confidence 90%

MITRE ATT&CK
T1059.005 Visual Basic

The presence of legacy WordBasic macro virus markers like 'TOOLSMACRO' and the 'AUTOEXEC' and 'AUTOOPEN' keywords strongly indicate a malicious macro embedded within the document. The OLE slack anomaly further suggests the file's structure has been manipulated, a common tactic for obfuscating malicious content. ClamAV detection as 'Win.Trojan.Mark-1' corroborates the malicious nature.

Heuristics 5

  • ClamAV: Win.Trojan.Mark-1 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Win.Trojan.Mark-1
  • 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
    OLE file is 46,080 bytes but its declared streams total only 26,414 bytes — 19,666 bytes (43%) 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).
  • 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 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
embedded_office_off00002061.ole embedded-office Embedded OLE/CFB Office body inside ole container at offset 0x2061 37791 bytes
SHA-256: 6079974613554310383a37c7a4bb59a7298d8dfb8c14288496fa446c18db7a57
embedded_office_off00005c14.ole embedded-office Embedded OLE/CFB Office body inside ole container at offset 0x5C14 22508 bytes
SHA-256: f7213603c5270306d4fa7399a505ecb61a4f6ae6505a3c04506a07a9193bcd88

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