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

Static analysis result for SHA-256 18ebbe611015cb12…

MALICIOUS

Office (OOXML) / .XLSX

24.5 KB Created: 2006-09-16 00:00:00 UTC Authoring application: Microsoft Excel 14.0300
MD5: b69022c2fc76a87f01c3da27be30149e SHA-1: 3f364ad7e93e2d9c37c2742fcc0b8e3886cf4a17 SHA-256: 18ebbe611015cb12da92e20ac09700d0057e810b36110db22f218795bd9b403a
120 Risk Score

Malware Insights

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

The sample is an Excel 4.0 macro sheet that contains strings indicative of downloading and executing a file. The heuristics indicate the use of WinAPI functions like URLDownloadToFileA and ShellExecuteA, strongly suggesting the intent to download and run a second-stage payload. The specific functions and the presence of an executable path point towards a downloader or dropper functionality.

Heuristics 2

  • Excel 4.0 macro sheet (1 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. The macro sheet is stored as XLSB/BIFF12 binary content, which many XML-only OOXML scanners miss.
  • Binary XLM macro sheet with WinAPI/download strings critical OOXML_XLM_BINARY_WINAPI_STRINGS
    Excel 4.0 macro sheet is stored as BIFF12/XLSB binary data and contains Win32 download or process-execution API strings such as URLDownloadToFileA, ShellExecuteA, or CreateDirectoryA. These strings are high-signal in XLM macro sheets and catch payload-download macros that XML-formula scanners cannot parse.

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
xlm_sheet_00.bin
99a6a52acb8f5c734f6d86faf89e0637a94ac99f953aa583d2658b47d2e1f9b9
xlm-macrosheet OOXML XLM macro sheet: xl/macrosheets/sheet1.bin 194023 bytes