Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 ac8ad9153e36a3d3…

MALICIOUS

Office (OLE)

59.5 KB Created: 2015-01-19 13:05:00 Authoring application: Microsoft Office Word First seen: 2015-03-15
MD5: 69cae61ee51a05ce37f95cce50b12495 SHA-1: 7ce71c27cc258e6bc10c20982236cc33673062f4 SHA-256: ac8ad9153e36a3d3644f890770259bcd8c77a10c0eff512b4a1fccecc3eb9e26
124 Risk Score

Malware Insights

MITRE ATT&CK
T1059.005 Visual Basic T1204.002 Malicious File

The sample contains a legacy WordBasic auto-exec marker ('autoopen') and evidence of VBA p-code execution, indicating an attempt to run malicious code upon opening. The heuristic 'OLE_VBA_PCODE_AUTOEXEC_EXEC' specifically points to the use of 'CreateObject' within an auto-exec macro. This functionality is commonly used to download and execute a second-stage payload, as suggested by the embedded URL.

Heuristics 5

  • ClamAV: Doc.Dropper.Agent-6412232-1 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Doc.Dropper.Agent-6412232-1
  • 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.
  • 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://laikah.de/js/bin.exe In document text (OLE body)