Malicious Office (OOXML) / .XLSM — malware analysis report

Static analysis result for SHA-256 d4b485dfba9cb256…

MALICIOUS

Office (OOXML) / .XLSM

112.1 KB Created: 2015-06-05 18:19:34 UTC Authoring application: Microsoft Excel 16.0300
MD5: 93bfb52566e105a031cb058a2b883a55 SHA-1: acc380f7680131e277bb8b716c65271a5ed5685c SHA-256: d4b485dfba9cb256c50b89bc3c137bb390d81e001fc6a0391b704b4de1602cd2
188 Risk Score

Malware Insights

MITRE ATT&CK
T1059.005 Visual Basic for Applications T1059.001 PowerShell T1204.002 Malicious File T1105 Ingress Tool Transfer

The sample is an XLSM file containing Excel 4.0 macros, including an Auto_Open macro. These macros utilize dangerous XLM functions like FORMULA and EXEC to download and execute a payload from one of the provided URLs. The presence of hidden sheets further suggests an attempt to conceal malicious activity. The script's intent is to download and execute a second-stage payload from the embedded URLs.

Heuristics 6

  • Excel 4.0 macro sheet (3 sheet(s)) critical OOXML_XLM_MACROSHEET
    Spreadsheet 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: FORMULA, HALT, GOTO, REGISTER, EXEC critical OOXML_XLM_DANGEROUS_FN
    Excel 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.
  • Auto_Open macro high OLE_VBA_AUTO
    Auto_Open macro
  • VBA project inside OOXML medium OOXML_VBA
    Document contains vbaProject.bin — VBA macros present
  • Hidden worksheet (hidden) low OOXML_HIDDEN_SHEET
    Excel workbook contains 3 hidden sheet(s) — hidden sheets are commonly used to conceal macro code, staging data, or intermediate payload construction
  • 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://185.45.193.80/44313,6048108796.dat
    • http://82.118.21.70/44313,6048108796.dat
    • http://45.144.31.232/44313,6048108796.dat
    • http://185.45.193.80/
    • http://82.118.21.70/
    • http://45.144.31.232/
    • 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
    • http://schemas.microsoft.com/office/spreadsheetml/2014/revision
    • http://schemas.microsoft.com/office/spreadsheetml/2015/revision2
    • http://schemas.microsoft.com/office/spreadsheetml/2016/revision3
    • http://schemas.microsoft.com/office/spreadsheetml/2016/revision6

Extracted artifacts 5

Files carved from inside the sample during analysis.

FilenameKindSourceSize
macros.bas
336c54ce55c4f97b2e578c36c24779a5cbf4053bf1babc3f97ec244f65df85ae		 vba-macro oletools.olevba.extract_macros (decoded VBA source from OOXML) 1451 bytes
vbaProject_00.bin
fd66c192343c5417fd652cf06eb25c1c94f77422491ceeb13938b68483d9178d		 vba-project OOXML VBA project: xl/vbaProject.bin 16384 bytes
xlm_sheet_00.xml
70da6d0347c5eb950708e32f28433a445cdbeb1ffd96ec2bad7f8e28050f1815		 xlm-macrosheet OOXML XLM macro sheet: xl/macrosheets/sheet1.xml 3816 bytes
xlm_sheet_01.xml
195a22194deb18d457e7a276044a8954c5a468f56b51b6a1ff34e52b2b6585ae		 xlm-macrosheet OOXML XLM macro sheet: xl/macrosheets/sheet2.xml 2129 bytes
xlm_sheet_02.xml
790f162dfe4d36146f6098416bb54d0d0a33d67d88c8fea35d57cce261bdd8f0		 xlm-macrosheet OOXML XLM macro sheet: xl/macrosheets/sheet3.xml 1943 bytes

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