Malicious Office (OLE) / .XLS — malware analysis report

Static analysis result for SHA-256 7877264fafa365b5…

MALICIOUS

Office (OLE) / .XLS

752.0 KB Created: 2010-02-23 04:12:47 Authoring application: Microsoft Excel
MD5: 508f2ea7c5f7c609050c3edae079f288 SHA-1: 4efd8c0cef649bb5b7878a50df84469fe80b957d SHA-256: 7877264fafa365b537f9d06aff42b66fe89f46528e6d69e03ecc951ccd50f500
248 Risk Score

Malware Insights

MITRE ATT&CK
T1059.005 Visual Basic T1203 Exploitation for Client Execution

The file is an Excel spreadsheet containing Excel 4.0 (XLM) macros, indicated by multiple critical heuristic firings including OLE_XLM_AUTOOPEN and OLE_XLM_DANGEROUS_FN. The presence of the RUN function within these macros suggests an attempt to execute arbitrary code, likely for downloading and executing a secondary payload. The heuristics also mention legacy macro-virus family markers like XL4Poppy and Normal_MacroVirus, but no specific family could be confidently identified.

Heuristics 5

  • Excel 4.0 (XLM) Auto_Open + macro sheet critical OLE_XLM_AUTOOPEN
    Workbook contains an Auto_Open / Auto_Close defined name together with an Excel 4.0 macro sheet — the canonical XLM auto-execution shape used by malware families such as Emotet and QakBot.
  • Excel 4.0 Auto_Open defined name critical OLE_XLM_AUTOOPEN_DEFINEDNAME
    oletools recovered an Auto_Open / Auto_Close entry from an Excel 4.0 macro sheet. The raw BIFF name can be tokenized or partially opaque to byte-string checks, but the recovered macro listing confirms the workbook has an XLM auto-execution entry.
  • XLM Auto_Open with dangerous formula APIs critical OLE_XLM_DANGEROUS_FN
    Excel 4.0 macro sheet contains an Auto_Open / Auto_Close entry and dangerous XLM formula APIs that can invoke programs, write files, or transfer control without VBA.
  • Legacy XLM macro-virus family marker critical OLE_XLM_LEGACY_MACRO_VIRUS
    Workbook contains an Excel 4.0 macro Auto_Open chain and legacy macro-virus family strings. This is a narrow indicator for infected XLM workbooks rather than ordinary formula use.
  • VBA project contains no executable statements low OLE_VBA_MACROS
    Document contains a VBA project, but extracted modules only contain attributes/options/comments and no executable statements.

Extracted artifacts 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
xlm_macros.txt
dfba19caee51d1879f39990b02359f7e7f09bbd67b6f9bc86113df6baed8d550		 xlm-macro oletools.olevba.extract_all_macros (XLM macro listing) 169068 bytes
macros.bas
481031c20227961d1e7d207d0bb17c79a9001efbdb37ac509a4ff93acb047bf0		 vba-macro oletools.olevba.extract_macros (decoded VBA source) 606 bytes

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