Malware Insights
This XLSM file contains Excel 4.0 macros, indicated by the 'OOXML_XLM_MACROSHEET' and 'OOXML_XLM_DANGEROUS_FN' heuristics. The 'VBA ActiveX event runs worksheet-decoded XLM formulas' heuristic suggests that the VBA code is used to trigger the XLM macros. The XLM macro sheet contains a dangerous `RETURN()` function, which can be used to execute arbitrary code. The VBA script attempts to decode and execute content, and the `MsgBox(Run(...))` line within the `VDecso` function is highly suspicious and likely used to execute the decoded XLM payload. The presence of a hidden sheet further supports the concealment of malicious activity.
Heuristics 6
-
VBA ActiveX event runs worksheet-decoded XLM formulas critical OLE_VBA_ACTIVEX_XLM_CELL_STAGERVBA code attached to an ActiveX/UserForm event reconstructs formula text from worksheet constants using Split/Replace/Mid or character shifting, then executes it through ExecuteExcel4Macro or Run. This is a high-confidence malware stager that hides XLM formula execution in sheet cells; it is not a document-parser CVE.
-
Excel 4.0 macro sheet (1 sheet(s)) critical OOXML_XLM_MACROSHEETSpreadsheet contains an Excel 4.0 (XLM) macro sheet — XLM was a major Office malware vector during 2020-2022 and evaded many VBA-focused controls before Microsoft tightened XLM defaults. Even legitimate XLM use is rare in modern workbooks.
-
Dangerous XLM formula APIs: RETURN critical OOXML_XLM_DANGEROUS_FNExcel 4.0 macro sheet uses formula APIs that call directly into Win32 (=CALL/=EXEC/=REGISTER/=FORMULA). These are the primitives used to download payloads, write files, and start processes from an XLM macro without invoking VBA.
-
VBA project inside OOXML medium OOXML_VBADocument contains vbaProject.bin — VBA macros present
-
Hidden worksheet (hidden) low OOXML_HIDDEN_SHEETExcel workbook contains 1 hidden sheet(s) — hidden sheets are commonly used to conceal macro code, staging data, or intermediate payload construction
-
Embedded URL info EMBEDDED_URLOne 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/spreadsheetml/2006/main
- http://schemas.microsoft.com/office/excel/2006/main
- http://schemas.openxmlformats.org/officeDocument/2006/relationships
- http://schemas.openxmlformats.org/markup-compatibility/2006
- http://schemas.microsoft.com/office/spreadsheetml/2009/9/ac
Extracted artifacts 4
Files carved from inside the sample during analysis.
| Filename | Kind | Source | Size |
|---|---|---|---|
macros.bas0ed9b61384fd84f7ec6edaeeb5c9792ddf894c42248678b8191b53a8f9852b3b |
vba-macro | oletools.olevba.extract_macros (decoded VBA source from OOXML) | 1758 bytes |
vbaProject_00.binfa1dc8ae18343d6ef2f429ac66dbfcc8c22090eebe818fe5b655839a29a39b68 |
vba-project | OOXML VBA project: xl/vbaProject.bin | 18432 bytes |
emf_00.emf18442f66fc184308368fb113b1c28494dce7331a052469405fcf94f2ee8085b5 |
ooxml-emf | OOXML EMF part: xl/media/image1.emf | 2024 bytes |
xlm_sheet_00.xmlbc9c6ebf0fd320628e241812b20c7929365b4e65eb917fa20596b9adfe330f8f |
xlm-macrosheet | OOXML XLM macro sheet: xl/macrosheets/sheet1.xml | 957 bytes |
Open this report in the interactive analyzer, or submit your own file for analysis.