Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 f5234cba1ff1e0d5…

MALICIOUS

Office (OLE)

62.8 KB First seen: 2019-09-30
MD5: d107a3af61f8b50d226a0d3eead490e5 SHA-1: f6ae212ca5880cec408cfb914419959c01d155b7 SHA-256: f5234cba1ff1e0d5967985d57de8bd69b4cb899adbdd30ee5013a025b8b004fa
102 Risk Score

Malware Insights

MITRE ATT&CK
T1059.005 Visual Basic T1566.001 Spearphishing Attachment

The sample contains a legacy WordBasic auto-exec marker (AutoOpen) and a high-severity heuristic firing for VBA p-code auto-exec with execution tokens (CreateObject). Although VBA extraction failed, these indicators strongly suggest the document is designed to run malicious code upon opening, likely delivered as a spearphishing attachment. The specific payload and execution method beyond the initial macro are not discernible from the provided evidence.

Heuristics 4

  • Reference to Windows Script Host high SC_STR_WSCRIPT
    Reference to Windows Script Host
  • VBA p-code auto-exec with execution tokens high OLE_VBA_PCODE_AUTOEXEC_EXEC
    Compiled VBA/cache stream contains an auto-execution token together with shell/download/object-execution tokens. This catches p-code-only or source-extraction-failure macro documents where visible source is unavailable.
  • 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
    The Analyzer could not extract VBA macros: the document may be legacy, encrypted or malformed.

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