Malicious Office (OLE) — malware analysis report

Static analysis result for SHA-256 f0e520bffb9fbf2c…

MALICIOUS

Office (OLE)

13.0 KB Created: 1601-01-01 00:00:00 Authoring application: Microsoft Word 6.0 First seen: 2012-06-14
MD5: af99651df2dcb984537e9a033d0ef4dd SHA-1: 894007c48c61d01b8ff46ccba17f1d09100d4f24 SHA-256: f0e520bffb9fbf2cb324a1b50a113bee730c144956942a3f29ad8484b4ed738d
160 Risk Score

Malware Insights

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

The file contains a legacy WordBasic AutoClose macro, indicated by the OLE_LEGACY_WORDBASIC_AUTOEXEC heuristic. This macro is designed to execute automatically when the document is closed. The presence of this macro, combined with ClamAV detecting it as Doc.Trojan.Helper-1, strongly suggests it's used to download and execute a secondary malicious payload. The document body contains common text that might be used in a lure, but the primary malicious functionality appears to be driven by the macro.

Heuristics 4

  • ClamAV: Doc.Trojan.Helper-1 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Doc.Trojan.Helper-1
  • 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_off00001c80.ole embedded-office Embedded OLE/CFB Office body inside ole container at offset 0x1C80 6016 bytes
SHA-256: 08925b3b66bb6efbd8634da84fd02d7b91f5e83b46d656a83cf826970c16bbb8

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