Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 990a762eb1c05e6e…

MALICIOUS

Office (OLE)

146.9 KB First seen: 2019-03-18
MD5: 5ef14b1a0c600108732779f53636705b SHA-1: 697f0b39bfa9792dd0284a9d91fa7995fdc5b83f SHA-256: 990a762eb1c05e6eeddd455a55f0cc225657c0c37784de7db45ed5c7d4905962
64 Risk Score

Malware Insights

MITRE ATT&CK
T1059.005 Visual Basic

The sample is an OLE file that contains a legacy WordBasic auto-exec macro named 'Autoopen'. This macro is flagged for attempting to execute a shell command. While VBA extraction failed, the presence of the auto-exec marker and the execution flag strongly indicate malicious intent. The specific shell command executed is not discernible due to the inability to extract VBA code.

Heuristics 4

  • 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
    olevba could not extract VBA macros (TypeError); format-agnostic byte-level scans still ran. Likely legacy, encrypted, or malformed OLE/OOXML — re-scanning the same bytes will yield the same outcome.
  • Embedded URL info EMBEDDED_URL
    One or more URLs were extracted from the document. The URL itself is not a detection — see the per-URL labels for which channel (macro, JS, link annotation, document body, ...) reached each URL.
    URL http://schemas.openxmlformats.org/drawingml/2006/main In document text (OLE body)

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