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

Static analysis result for SHA-256 2afa0d9523e648ce…

MALICIOUS

Office (OOXML) / .XLSX

26.3 KB Created: 2006-09-16 00:00:00 UTC Authoring application: Microsoft Excel 14.0300
MD5: 18a81c1152d399c128564e0d16170c20 SHA-1: 3f48a9e4d24094613727f36185a6392b3a9c9d2b SHA-256: 2afa0d9523e648ce0e5e4976a28e63d3a24cb968fb95818b337422e361a07ffe
182 Risk Score

Malware Insights

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

This Excel 4.0 macro-enabled XLSX file contains embedded macros that leverage WinAPI functions like URLDownloadToFileA and ShellExecuteA. The primary intent appears to be downloading and executing a second-stage payload from the URL http://jdsofttech.com/ds/3.gif, indicated by the presence of download and execution-related strings within the macro sheet.

Heuristics 4

  • 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.
  • URL reconstructed from XLM cell array (1 URL) critical OOXML_XLM_CELL_ARRAY_URL
    Excel 4.0 macro sheet stages its payload URL across individual numeric cells (one ASCII charcode per cell) or inside an embedded HTA that uses VBScript Chr()/&-concat obfuscation. The reconstructed URL is invisible to literal-bytes URL extraction because it is never contiguous in the workbook stream. URLs were recovered by walking the BIFF12 record stream of every worksheet and macrosheet part and decoding RK/inline-string cells in both row-major and column-major order.
  • 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://jdsofttech.com/ds/3.gif

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
xlm_sheet_00.bin
353cb9e320e769bd0172c949754a12b71aae8fc508fdcdd3a2c593938b07a06a		 xlm-macrosheet OOXML XLM macro sheet: xl/macrosheets/sheet1.bin 200427 bytes

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