Win.Trojan.Concept-8 — Office (OLE) malware analysis

Static analysis result for SHA-256 7292667e1cd5e0fc…

MALICIOUS

Office (OLE)

21.5 KB Created: 1993-09-28 15:08:00 Authoring application: Microsoft Word for Windows 95 First seen: 2012-06-14
MD5: 1e21edb492cc821a4e1a17a33ea60917 SHA-1: 0f0cb3af936c8183dde21e4db22ab39c2bca13cb SHA-256: 7292667e1cd5e0fcae8eb801d592a4b577e0a7feb1e75a2ce7eb3c183f84bdb4
160 Risk Score

Malware Insights

Win.Trojan.Concept-8 · confidence 95%

MITRE ATT&CK
T1059.005 Visual Basic

The file is identified as a legacy Word document containing WordBasic macros, specifically triggering the 'FileSaveAs' auto-exec marker. The presence of embedded OLE objects with suspicious static findings, including empty streams and a FAT chain loop, further indicates malicious intent. ClamAV detection confirms this as Win.Trojan.Concept-8, suggesting a trojan dropper or similar payload.

Heuristics 4

  • ClamAV: Win.Trojan.Concept-8 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Win.Trojan.Concept-8
  • 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 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_off00002100.ole embedded-office Embedded OLE/CFB Office body inside ole container at offset 0x2100 13568 bytes
SHA-256: 845da91ccdef76bcd3f804c3eb97dce3f75ff3b039f9cfd386de9c7a39a9e3b4