Valyria — Office (OOXML) / .XLSM malware analysis

Static analysis result for SHA-256 6df08a0f239a7e60…

MALICIOUS

Office (OOXML) / .XLSM

2.67 MB Created: 2020-02-01 18:28:07 UTC Authoring application: Microsoft Excel 12.0000
MD5: 4dce6cd773fee29897d77b670c278cba SHA-1: 2e952383f0ab1d2efe9fd728013f633e76f77c5c SHA-256: 6df08a0f239a7e606968d876ee7237a1f31c73d102a9acd701aaf2b83f49f4c8
202 Risk Score

Malware Insights

Valyria · confidence 95%

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

The critical heuristic 'OFFICE_EMBEDDED_MACRO_OBJECT' and the ClamAV detection 'Xls.Dropper.Valyria-10030821-0' indicate this is a macro-enabled dropper. The VBA p-code auto-execution with SHELL execution tokens strongly suggests the macro attempts to download and run a secondary payload, consistent with a dropper's function. The file is likely delivered as a spearphishing attachment.

Heuristics 6

  • Embedded Office object carries macros critical OFFICE_EMBEDDED_MACRO_OBJECT
    This document embeds a second Office file that itself contains a VBA macro project or an Excel 4.0 (XLM) macro sheet. Hiding a macro-bearing workbook or document inside another document — frequently under an obfuscated, non-standard part name — is a macro-smuggling technique that defeats scanners which only inspect the outer document's macro storage. No benign authoring workflow stages a hidden macro project this way.
  • ClamAV: Xls.Dropper.Valyria-10030821-0 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Xls.Dropper.Valyria-10030821-0
  • 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.
  • VBA project inside OOXML medium OOXML_VBA
    Document contains a VBA project — VBA macros present
  • Embedded OLE object medium OOXML_OLE_OBJECT
    Document contains an embedded OLE object
  • Large OOXML part skipped info SCAN_INCOMPLETE
    One or more high-value OOXML parts exceeded the scanner's per-entry size cap and may not have been fully inspected.

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