how it happened
- whoseveral attacker groupsMicrosoft names two China-based state groups and Storm-2603
- the gapinternet-facing SharePointon-premises servers, login bypassed
- thenmachine keys copiedthe secrets that sign the server's own data
- the resultaccess outlives the patchuntil keys are rotated and backdoors removed
what everyone assumed
Neither Microsoft nor the affected organisations have said what they believed beforehand, so this belief is an inference from the guidance that followed. It is the normal way vulnerabilities are handled. A vendor ships a fix, the server gets the update, and the hole is closed. For companies that kept SharePoint on their own servers, patching can be the one security task that is scheduled and checked, sometimes by an outside IT firm. Once the version number is right, the ticket closes.
That works when the attacker’s way in is the flaw itself. It fails when the attacker used the flaw to take something the patch does not touch.
what happened
On 8 July 2025 Microsoft published fixes for two SharePoint Server flaws, CVE-2025-49706 (spoofing) and CVE-2025-49704 (code execution), according to their CVE records. Microsoft’s Threat Intelligence blog of 22 July 2025 says its analysis suggests attackers were trying to exploit them as early as 7 July. Researchers at Eye Security wrote on 19 July that they identified a malicious page on a customer’s on-premises server on the evening of 18 July, saw what they called a probable test wave on 17 July, and then found compromised servers across the internet. The chain became known as “ToolShell”.
On 19 July Microsoft’s Security Response Center published guidance for a new identifier, CVE-2025-53770, and on 20 July added CVE-2025-53771. Microsoft’s blog describes the first as related to CVE-2025-49704 and the second as a security bypass for CVE-2025-49706. Updates for SharePoint Subscription Edition and SharePoint 2019 followed, and SharePoint 2016 updates came on 21 July. Only on-premises servers were affected. Microsoft states that SharePoint Online in Microsoft 365 was not.
The part that matters for access is what the attackers took. Microsoft’s blog says the dropped file, spinstall0.aspx, “contains commands to retrieve MachineKey data”, enabling the theft of the key material. CISA’s malware analysis of 6 August 2025 shows the same file writing out the server’s ValidationKey and DecryptionKey, and a second file that slips the keys into a response header.
What the keys do. ASP.NET uses these machine keys to sign and protect data a web page sends back and forth with the browser, called ViewState. Microsoft explained in a separate blog on 6 February 2025 that an attacker holding the keys can craft a ViewState the server accepts, which gives code execution on the server. Eye Security applied that to ToolShell: with the stolen keys, attackers could send validly signed payloads to the server “even after patching”, in the researchers’ words.
What Microsoft asked for. The MSRC guidance, from its revision of 20 July 2025, says it is critical that customers rotate the SharePoint ASP.NET machine keys and restart IIS on all SharePoint servers after applying the updates or enabling Microsoft’s antimalware scanning. It names the two PowerShell commands that generate and deploy new keys. CISA’s alert, revised to 6 August 2025, goes further: rotate the keys, apply the update, rotate the keys again, then restart IIS, and remove any malicious modules from the server’s configuration first, because they otherwise reload on restart.
Microsoft attributes the activity to two China-based state groups it calls Linen Typhoon and Violet Typhoon, and to a group it calls Storm-2603, which it assesses with moderate confidence to be China-based. From 18 July 2025, Microsoft says, Storm-2603 used the flaws to deploy ransomware, named as Warlock in its update of 23 July.
step by step
- 8 July 2025Microsoft fixes two SharePoint flawsThe CVE records for CVE-2025-49704 and CVE-2025-49706 are published with the July security updates.
- 18 July 2025mass exploitation is spottedEye Security, in vendor research, identifies a web shell on a customer's on-premises SharePoint server and starts scanning for others.
- 19 to 21 July 2025new CVEs and new updatesMicrosoft publishes guidance for CVE-2025-53770 and CVE-2025-53771, then updates for Subscription Edition, 2019 and 2016.
- 20 July 2025the patch is not the endMicrosoft's guidance adds that customers must rotate the servers' machine keys and restart IIS after updating; researchers warn that keys stolen before the patch still work.the assumption breaks here
- 24 July to 6 August 2025ransomware and malware analysisCISA adds ransomware deployment to its alert and publishes an analysis of the files, including the one that dumps the keys.
how it surfaced
Eye Security, in vendor research, reported on 19 July 2025 that it had found more than 400 actively compromised systems after scanning over 23,000 SharePoint servers worldwide. Its update of 29 July said over 8,000 systems remained exposed online. No government or Microsoft source opened for this page gives a count of victims.
The record also corrected itself. CISA updated its alert on 22 July 2025 to name CVE-2025-49706 and CVE-2025-49704 as the exploited flaws. Eye Security revised its page on 29 July, dropping the zero-day label because those flaws had been patched on 8 July, and noting that code execution could also happen in memory without a file on disk. CISA added CVE-2025-53770 to its Known Exploited Vulnerabilities catalog on 20 July 2025 and the two earlier flaws on 22 July. The catalog’s required action tells owners to disconnect public-facing SharePoint Server 2013 and earlier, which no longer receive fixes.
Key rotation is not the finish line either. Microsoft’s February 2025 blog warns that rotating machine keys will not remove backdoors an attacker already planted, and CISA’s alert treats the hunt for web shells and malicious modules as a separate step. The shape matches CitrixBleed, where patched appliances left stolen sessions working, and Storm-0558, where one stolen signing key let attackers mint their own access.
A patch fixes the code. A secret the attacker copied keeps working until you replace it.
On every server you patched in a hurry, ask which keys, passwords and certificates it held, and whether any of them changed afterwards.
picture it at a company like yours
The company here is made up. The other two paths are not: they happened, and each links to the story.
- in this storythe day it mattersSomeone copies that key through a flaw, and when the update goes in the next week, the copied key keeps opening the server.what it costs youThe ticket says patched and closed, while a stranger can still run commands on the machine that holds your contracts and HR files.
- or it goes like thisit happenedMicrosoft AI data exposure, 2023howA share link meant for one folder opens the whole storage account.what leavesbackups, passwords and private messageswho ends up with itanyone who finds the link
- or it goes like thisit happenedPower Apps misconfiguration, 2021howA default on a no-code app leaves its data readable without logging in.what leavespersonal records you collectedwho ends up with itanyone who looks
sources
- Microsoft Security Response Center: Customer guidance for SharePoint vulnerability CVE-2025-53770, 19 July 2025 (revisions to 23 July 2025)
- Microsoft Threat Intelligence: Disrupting active exploitation of on-premises SharePoint vulnerabilities, 22 July 2025 (updated 23 July 2025)
- Microsoft Threat Intelligence: Code injection attacks using publicly disclosed ASP.NET machine keys, 6 February 2025
- CISA: UPDATE: Microsoft Releases Guidance on Exploitation of SharePoint Vulnerabilities, 20 July 2025 (last revised 6 August 2025)
- CISA: MAR-251132.c1.v1 Exploitation of SharePoint Vulnerabilities (AR25-218A), 6 August 2025
- CISA: Known Exploited Vulnerabilities Catalog (JSON feed, catalogVersion 2026.11.10)
- CVE record CVE-2025-53770 (Microsoft as CNA), published 20 July 2025
- CVE record CVE-2025-49704 (Microsoft as CNA), published 8 July 2025
- Eye Security: SharePoint Under Siege: ToolShell exploit (CVE-2025-49706 and CVE-2025-49704), 19 July 2025, updated to 29 July 2025 (vendor research)
your turn
what you can do about it
this week
Ask who runs your on-premises SharePoint or other internet-facing web server when its machine keys were last changed.
If the answer is "never" or nobody knows, that server was set up with secrets that outlive every update. Microsoft's July 2025 guidance asked for new machine keys and a restart of IIS on every SharePoint server, and CISA asked for a check for planted web shells and modules on top. If the server still runs SharePoint 2013 or older, CISA's instruction is to take it off the internet. [The guide on the box at the edge](/read/edge-devices) covers who owns these servers, and [the token guide](/read/token-lives-forever) covers why a credential stays valid until someone ends it. Which of your servers would still let a stranger in after next month's patch?
go deeper
if you're not sure where to start
Run the offboarding checklist on one leaver. It covers every account and token to close when someone leaves.
open the checklist →
