Process

unknown

excel.exe

excel.exe is Microsoft Excel, the spreadsheet application in Microsoft Office. Like Word, it is a frequent malware entry point: a weaponized workbook is opened and a macro runs code. Excel is notable for two macro systems, modern VBA and the legacy Excel 4.0 (XLM) macros that long evaded detection.

File identity

File details

Not observed.

Signing information

Not observed.

File version0

Not observed.

File size0

Not observed.

Execution context

File paths0

Not observed.

User context0

Not observed.

Integrity level0

Not observed.

Instances0

Not observed.

Session0

Not observed.

Token privileges0

Not observed.

Ancestry

Parents0

Not observed.

Children0

Not observed.

Grandparents0

Not observed.

Grandchildren0

Not observed.

Behavior

Loaded modules0

Not observed.

Named pipes0

Not observed.

Process handles0

Not observed.

Command-line patterns0

Not observed.

LOLBAS1
  • Excel.exe {REMOTEURL}Download · It will download a remote payload and place it in INetCache.

Indicators

Hashes

Not observed.

Analysis

About this process

excel.exe is the Excel application, opening and editing workbooks (.xls, .xlsx, .xlsm, .xlsb). It supports two kinds of macros: Visual Basic for Applications (VBA), shared with the rest of Office, and the older Excel 4.0 macro language (XLM) stored in macro sheets, which attackers favored because many tools did not parse it. Excel is part of Microsoft Office, installed under C:\Program Files\Microsoft Office (or the (x86) path), signed by Microsoft.

Legitimately, excel.exe is opened by users to work with spreadsheets, parented by explorer.exe or launched from Outlook or a browser. Working in a workbook is unremarkable. Excel starting another program is not.

Security notes

excel.exe is a top initial-access and execution vector (T1204.002). A user opens a workbook and a macro runs the payload (T1059.005). Excel carries an extra wrinkle: alongside VBA, the legacy Excel 4.0 (XLM) macro language ran code from macro sheets and went undetected by many tools for years, making XLM-laden workbooks a favored delivery method. Either way, the recognizable evidence is Excel spawning a shell or script host, excel.exe as the parent of powershell.exe, cmd.exe, mshta.exe, or wscript.exe.

Excel is also a persistence surface (T1137), through macro-enabled templates and add-ins (including XLL add-ins) that load when Excel starts. New or unexpected template and add-in entries warrant review. Because Excel itself is legitimate, the children it spawns, its network activity, and changes to its startup items are what separate ordinary use from compromise.

Anomaly signals5
  • Image path outside the Microsoft Office install directoryhigh
  • excel spawning cmd.exe, powershell.exe, mshta.exe, wscript.exe, or rundll32.exehigh
  • A workbook containing Excel 4.0 (XLM) macro sheetshigh
  • Outbound network connections shortly after a workbook openshigh
  • A child process running from or writing to Temp or AppDatahigh

Telemetry

OS prevalence0

Not observed.

Observation timeline

Not observed.

References

Subsearch

Hasbeen seen inof excel.exe?