Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 182d20413b032af6…

MALICIOUS

Office (OLE)

42.5 KB Created: 2003-08-16 07:39:00 Authoring application: Microsoft Word 10.0 First seen: 2012-06-14
MD5: 311c96fb8b10066c1611a43bdd73a408 SHA-1: 90d027d3803661cc5aaea95c86b1d346f937cf3a SHA-256: 182d20413b032af6d84906b32ffab2110ac50fe08e50dc91f1fa1245a3b17dae
82 Risk Score

Malware Insights

MITRE ATT&CK
T1059.005 Visual Basic

The file is identified as malicious by ClamAV and contains markers for legacy WordBasic auto-exec macros, specifically 'AutoClose'. Although VBA macros could not be extracted due to an unsupported format, the presence of these markers strongly suggests an attempt to execute malicious code upon document interaction. The file's structure and the legacy macro marker indicate a potential for automated execution of a malicious payload.

Heuristics 3

  • ClamAV: Doc.Trojan.Kaffer-1 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Doc.Trojan.Kaffer-1
  • 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.
  • Unsupported Office format for VBA extraction info OFFICE_FORMAT_UNSUPPORTED
    olevba could not extract VBA macros (AssertionError); format-agnostic byte-level scans still ran. Likely legacy, encrypted, or malformed OLE/OOXML — re-scanning the same bytes will yield the same outcome.

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