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

Static analysis result for SHA-256 0352ba53c4ada087…

MALICIOUS

Office (OOXML) / .XLSX

24.5 KB Created: 2006-09-16 00:00:00 UTC Authoring application: Microsoft Excel 14.0300
MD5: ba7fd57a2d67b1706177508a911ebd1f SHA-1: 18262e1aa6d3dbf16b33ce55f535c3fc8ad2e5ad SHA-256: 0352ba53c4ada087911a7a753d1a7da043e9dd869252cbafce123f315cc58a30
120 Risk Score

Malware Insights

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

The file contains Excel 4.0 macros, indicated by the OOXML_XLM_MACROSHEET heuristic. The macros leverage WinAPI functions like URLDownloadToFileA and ShellExecuteA, suggesting an intent to download and execute a secondary payload. The presence of these download and execution strings points to an Ingress Tool Transfer and Malicious File execution attack pattern.

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