The SharePoint "ToolShell" Attacks: What On-Premises Server Owners Need to Do

For a lot of businesses, SharePoint is just "where the files live." It has been running on a server in the back room for years, doing its job quietly, and nobody has thought much about it. This month, that quiet server became one of the most targeted pieces of software on the internet.

Starting around July 18, security researchers spotted attackers mass-exploiting a previously unknown vulnerability in on-premises SharePoint Server. The attack chain, nicknamed "ToolShell," lets an attacker take control of an unpatched, internet-facing SharePoint server without logging in. Microsoft has released emergency fixes, but for anyone who was exposed, patching is only the beginning.

First: are you affected?

The most important point up front: SharePoint Online, the version included with Microsoft 365, is not affected. If your SharePoint is part of your Microsoft 365 subscription and you reach it at an address ending in sharepoint.com, Microsoft manages it and you do not need to take action for this issue.

The vulnerable products are the versions you install and run on your own servers:

  • SharePoint Server Subscription Edition
  • SharePoint Server 2019
  • SharePoint Server 2016

Older versions like SharePoint 2010 and 2013 are past end of support and do not receive security updates at all. If you are still running one of those, it should be taken off the internet and replaced.

What happened

The vulnerability, tracked as CVE-2025-53770, is related to flaws Microsoft had tried to fix in its July security updates. Attackers found a way around those fixes. By sending specially crafted requests to a vulnerable server, they could run their own code on it, no password required.

What made this attack especially nasty is what the attackers did next. In many cases they planted a small malicious file on the server and used it to steal the server's machine keys, the cryptographic secrets SharePoint uses to validate data it trusts. With those keys, an attacker can continue to get in and run commands even after the vulnerability is patched.

Microsoft released updates for Subscription Edition and 2019 on July 20 and for 2016 shortly after. CISA added the flaw to its list of known exploited vulnerabilities. Microsoft has said multiple threat groups, including state-linked actors, have been exploiting it, and security firms have reported compromises at hundreds of organizations, including government agencies.

If an attacker stole your server's keys before you patched, the patch locks the front door but leaves them holding a copy of the key.

What to do if you run SharePoint Server

Microsoft and CISA have published detailed guidance. In plain terms, the steps are:

  1. Apply the latest security update for your SharePoint version immediately.
  2. Make sure the Antimalware Scan Interface (AMSI) is enabled for SharePoint and that Microsoft Defender Antivirus or equivalent endpoint protection is running on the server.
  3. Rotate the ASP.NET machine keys on your SharePoint servers after patching, then restart IIS. This invalidates any keys an attacker may have stolen.
  4. Look for signs of compromise, including unfamiliar files in SharePoint's web folders and suspicious requests in the logs. Microsoft and security vendors have published specific indicators to check for.
  5. If you find evidence of compromise, treat it as a full incident. Attackers may have moved beyond SharePoint to other systems on your network.

If your server could not be patched promptly, Microsoft's advice was to disconnect it from the internet until it could be.

The bigger lesson: internet-facing servers need a real owner

ToolShell is not the first time this has happened. Small businesses got a painful version of the same lesson in 2021, when attackers mass-exploited on-premises Exchange servers. The pattern is consistent: a widely used Microsoft server product, installed on-premises and reachable from the internet, gets a critical flaw, and attackers scan the entire internet for vulnerable systems within hours.

In that environment, "we patch when we get around to it" is not a strategy. Any server you expose to the internet needs someone responsible for:

  • Watching for emergency security advisories, not just monthly updates.
  • Applying critical patches within days, sometimes within hours.
  • Following through on the extra steps, like key rotation, that advisories often require.
  • Monitoring the server for signs that something is wrong.

Should you still be running SharePoint on your own server?

This is the harder question, and it deserves an honest answer. There are good reasons some organizations keep SharePoint on-premises, such as custom applications, specific compliance requirements, or integration with other in-house systems. But for many small businesses, on-premises SharePoint is simply the result of a decision made years ago that nobody revisited.

SharePoint Online in Microsoft 365 offers most of the same document-management features, and Microsoft handles the patching. Many businesses already pay for it through their Microsoft 365 licenses without using it. Microsoft has also announced that SharePoint Server 2016 and 2019 will reach end of support in July 2026, so anyone on those versions needs a plan within the next year anyway.

Your checklist

  1. Confirm whether you run SharePoint on your own server or only through Microsoft 365.
  2. If on-premises: patch, enable AMSI, rotate machine keys, and restart IIS.
  3. Check for indicators of compromise and investigate anything suspicious.
  4. Review whether the server truly needs to be reachable from the internet.
  5. Make sure someone is assigned to watch for and act on emergency advisories.
  6. Start planning a migration or upgrade before the 2016 and 2019 end-of-support date.

We can help

On-premises servers are not going away overnight, but they need attentive care. Rapid patching, monitoring, and migration planning are the core of our server administration services. If you are not sure whether your SharePoint server was exposed, or you want help moving to SharePoint Online, email info@pinellasit.com or use our contact form.

Need help with this?

Talk to a local IT team that has supported businesses across Pinellas & Pasco County since 2010.

Get a Free Consultation Free Security Assessment