C0058: SharePoint ToolShell Exploitation
The SharePoint ToolShell Exploitation campaign was conducted in July 2025 and encompassed the first waves of exploitation against incompletely patched spoofing (CVE-2025-49706) and remote code execution (CVE-2025-49704) vulnerabilities affecting on-premises Microsoft SharePoint servers. Later patched and updated as CVE-2025-53770 and CVE-2025-53771, the ToolShell vulnerabilities were widely exploited including by China-based ransomware actor Storm-2603 and espionage actors Threat Group-3390 and ZIRCONIUM. SharePoint ToolShell Exploitation targeted multiple regions and industries including finance, education, energy, and healthcare across Asia, Europe, and the United States.[1][2][3][4][5]
Security context for executives and security teams
C0058: SharePoint ToolShell Exploitation describes The [SharePoint ToolShell Exploitation](https://attack.mitre.org/campaigns/C0058) campaign was conducted in July 2025 and encompassed the first waves of exploitation against incompletely patched spoofing (CVE-2025-49706) and remote code execution (CVE-2025-49704) vulnerabilities affecting on-premises Microsoft SharePoint servers. Later patched and updated as CVE-2025-53770 and CVE-2025-53771, the ToolShell vulnerabilities were widely exploited including by China-based ransomware actor Storm-2603 and espionage actor...
Executive priority
C0058: SharePoint ToolShell Exploitation is an official MITRE ATT&CK campaign. Glexia treats it as defensive behavior context for prioritizing monitoring, control validation, and response planning without using the object by itself as an attribution claim.
Technical view
Security teams should validate C0058: SharePoint ToolShell Exploitation by reviewing the official ATT&CK relationships, mapped tactics (the mapped ATT&CK tactic context), supported platforms (the platforms named in the official object), and available local telemetry before making detection or mitigation decisions.
Likely telemetry
- Official ATT&CK relationships and object metadata
Detection direction
- Validate whether C0058: SharePoint ToolShell Exploitation appears in your detection coverage and tabletop scenarios.
- Use the object to align executive risk language with SOC, incident response, and detection engineering work.
- Do not treat ATT&CK relationship context as attribution without corroborating evidence.
Mitigation priorities
- Map the object to existing controls and identify missing telemetry or response ownership.
- Prioritize mitigations that reduce exposure on the listed platforms and tactics.
- Review adjacent ATT&CK relationships before changing policy, detections, or reporting language.
Additional notes and limits
Baseline Glexia take generated from the official MITRE ATT&CK STIX object, source hash, tactics, platforms, and detection fields. It is safe to replace with a richer model-generated take for the same source hash later.
This baseline take is source-grounded and schema-validated, but it does not include environment-specific telemetry, incident evidence, or threat-intelligence corroboration.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
SharePoint ToolShell Exploitation
The SharePoint ToolShell Exploitation campaign was conducted in July 2025 and encompassed the first waves of exploitation against incompletely patched spoofing (CVE-2025-49706) and remote code execution (CVE-2025-49704) vulnerabilities affecting on-premises Microsoft SharePoint servers. Later patched and updated as CVE-2025-53770 and CVE-2025-53771, the ToolShell vulnerabilities were widely exploited including by China-based ransomware actor Storm-2603 and espionage actors Threat Group-3390 and ZIRCONIUM. SharePoint ToolShell Exploitation targeted multiple regions and industries including finance, education, energy, and healthcare across Asia, Europe, and the United States.[1][2][3][4][5]
How security teams should use this page
Treat this object as behavior context, not an attribution claim. Validate the related groups, software, data sources, and mitigations against official ATT&CK relationships and your own telemetry before making control-coverage decisions.
Techniques used
This mirrors the MITRE pattern of making group, software, campaign, and technique relationships scannable. Relationship notes come from mirrored ATT&CK relationship text when available.
| Domain | ID | Name | Relationship / procedure |
|---|---|---|---|
| Enterprise | T1053.005 | Scheduled TaskSub-technique | During SharePoint ToolShell Exploitation, threat actors used scheduled tasks to help establish persistence.[1] |
| Enterprise | T1033 | System Owner/User Discovery | During SharePoint ToolShell Exploitation, threat actors executed `whoami` on victim machines to enumerate user context and validate privilege levels.[1]CitationSentinelOne ToolShell JUL 2025 |
| Enterprise | T1552.001 | Credentials In FilesSub-technique | During SharePoint ToolShell Exploitation, threat actors accessed web.config and machine.config to extract MachineKey values, enabling them to forge legitimate VIEWSTATE tokens for future deserialization payloads.[1][3][5]CitationSentinelOne ToolShell JUL 2025[2] |
| Enterprise | T1027.002 | Software PackingSub-technique | During SharePoint ToolShell Exploitation, threat actors UPX-packed malicous payloads including 4L4MD4R ransomware.[2] |
| Enterprise | T1071.001 | Web ProtocolsSub-technique | During SharePoint ToolShell Exploitation, threat actors issued HTTP `POST` requests to web shells with spoofed or empty Referrer headers, to circumvent authorization controls.[1][3][5]CitationSentinelOne ToolShell JUL 2025[2] |
| Enterprise | T1083 | File and Directory Discovery | During SharePoint ToolShell Exploitation, threat actors leveraged commands to locate accessible file shares, backup paths, or SharePoint content.[1] |
| Enterprise | T1505.003 | Web ShellSub-technique | During SharePoint ToolShell Exploitation, threat actors followed exploitation of SharePoint servers with installation of a malicious .aspx web shell (spinstall0.aspx) that was written to the `_layouts/15/` directory, granting persistent HTTP-based access.[1][4][3][5]CitationSentinelOne ToolShell JUL 2025[2] |
| Enterprise | T1583.001 | DomainsSub-technique | During SharePoint ToolShell Exploitation, threat actors registered C2 domains to spoof legitimate Microsoft domains.[1][2] |
| Enterprise | T1140 | Deobfuscate/Decode Files or Information | During SharePoint ToolShell Exploitation, threat actors decrypted scripts prior to execution.[2] |
| Enterprise | T1484.001 | Group Policy ModificationSub-technique | During SharePoint ToolShell Exploitation, threat actors, including Storm-2603, modified group policy to enable ransomware distribution.[1] |
| Enterprise | T1003.001 | LSASS MemorySub-technique | During SharePoint ToolShell Exploitation, threat actors used Mimikatz to dump LSASS memory.[1] |
| Enterprise | T1059.001 | PowerShellSub-technique | During SharePoint ToolShell Exploitation, threat actors used PowerShell to execute attacker-controlled encoded commands.[1][3]CitationSentinelOne ToolShell JUL 2025[2] |
| Enterprise | T1657 | Financial Theft | During SharePoint ToolShell Exploitation, threat actors demanded ransom payments to unencrypt filesystems and to refrain from publishing sensitive data exfiltrated from victim networks.[2] |
| Enterprise | T1190 | Exploit Public-Facing Application | During SharePoint ToolShell Exploitation, threat actors exploited authentication bypass and remote code execution vulnerabilities (CVE-2025-49706 and CVE-2025-49704) against on-premises SharePoint servers. This activity was characterized by crafted `POST` requests to the ToolPane endpoint `/_layouts/15/ToolPane.aspx`.[1][4][3][5]CitationSentinelOne ToolShell JUL 2025[2] |
| Enterprise | T1047 | Windows Management Instrumentation | During SharePoint ToolShell Exploitation, threat actors used WMI for execution.[1] |
| Enterprise | T1119 | Automated Collection | During SharePoint ToolShell Exploitation, threat actors used a command shell to automatically iterate through web.config files to expose and collect machineKey settings.[5][2] |
| Enterprise | T1572 | Protocol Tunneling | During SharePoint ToolShell Exploitation, threat actors utilized ngrok tunnels to deliver PowerShell payloads.[1] |
| Enterprise | T1585.002 | Email AccountsSub-technique | During SharePoint ToolShell Exploitation, threat actors created Proton mail accounts for communication with organizations infected with ransomware.[2] |
| Enterprise | T1082 | System Information Discovery | During SharePoint ToolShell Exploitation, threat actors fingerprinted targeted SharePoint servers to identify OS version and running processes.[1] |
| Enterprise | T1486 | Data Encrypted for Impact | During SharePoint ToolShell Exploitation, threat actors deployed ransomware including 4L4MD4R and Warlock.[1][2] |
| Enterprise | T1074.001 | Local Data StagingSub-technique | During SharePoint ToolShell Exploitation, threat actors staged stolen data from web.config files to debug_dev.js.[2][5] |
| Enterprise | T1505.004 | IIS ComponentsSub-technique | During SharePoint ToolShell Exploitation, threat actors modified Internet Information Services (IIS) components to load suspicious .NET assemblies for persistence.[1] |
| Enterprise | T1059.003 | Windows Command ShellSub-technique | During SharePoint ToolShell Exploitation, threat actors utilized `cmd.exe` and batch scripts within the victim environment.[1][4][3]CitationSentinelOne ToolShell JUL 2025 |
| Enterprise | T1027.010 | Command ObfuscationSub-technique | During SharePoint ToolShell Exploitation, threat actors executed Base64-encoded PowerShell commands.[1][3][5]CitationSentinelOne ToolShell JUL 2025[2] |
| Enterprise | T1090 | Proxy | During SharePoint ToolShell Exploitation, threat actors used Fast Reverse Proxy to communicate with C2.[1][4] |
| Enterprise | T1685 | Disable or Modify Tools | During SharePoint ToolShell Exploitation, threat actors disabled Microsoft Defender through Registry settings and real-time monitoring via PowerShell.[1][2] |
| Enterprise | T1588.002 | ToolSub-technique | During SharePoint ToolShell Exploitation, threat actors leveraged tools including Impacket, PsExec, and Mimikatz.[1] |
| Enterprise | T1569.002 | Service ExecutionSub-technique | During SharePoint ToolShell Exploitation, threat actors leveraged PsExec for command execution and used `services.exe` to disable Microsoft Defender via Registry keys.[1] |
| Enterprise | T1112 | Modify Registry | During SharePoint ToolShell Exploitation, threat actors, including Storm-2603, disabled security services via Registry modifications.[1] |
| Enterprise | T1620 | Reflective Code Loading | During SharePoint ToolShell Exploitation, threat actors reflectively loaded payloads using `System.Reflection.Assembly.Load`.[1][3][5]CitationSentinelOne ToolShell JUL 2025[2] |
| Enterprise | T1595.002 | Vulnerability ScanningSub-technique | During SharePoint ToolShell Exploitation, threat actors scanned for SharePoint servers vulnerable to CVE-2025-53770.[2] |
| Enterprise | T1105 | Ingress Tool Transfer | During SharePoint ToolShell Exploitation, threat actors used a loader to download and execute ransomware.[2] |
| Enterprise | T1570 | Lateral Tool Transfer | During SharePoint ToolShell Exploitation, threat actors used Impacket to remotely stage and execute payloads via WMI.[1] |
| Enterprise | T1041 | Exfiltration Over C2 Channel | During SharePoint ToolShell Exploitation, threat actors exfiltrated stolen credentials and internal data over HTTPS to C2 infrastructure.[1] |
| Enterprise | T1005 | Data from Local System | During SharePoint ToolShell Exploitation, threat actors extracted information from the compromised systems.[1][4]CitationSentinelOne ToolShell JUL 2025[2] |
Groups, software, and campaigns
S0029: PsExec
S0002: Mimikatz
S0508: ngrok
S0357: Impacket
All related ATT&CK context
Object version and sync metadata
The fields below describe the current mirrored snapshot. When Glexia retains multiple ATT&CK source imports, you can open the table to compare the same object across releases (hashes and MITRE timestamps). For MITRE’s own release notes and roadmap, see ATT&CK resources — Updates.
Imported snapshots across ATT&CK releases(2)
| Release | Bundle imported | Object version | Modified | Status | Raw hash |
|---|---|---|---|---|---|
| 19.2 | 1.0 | Current bundle | db7a6069d86d… | ||
| 19.1 | 1.0 | Older bundle | 4725934193e7… |
Mirrored ATT&CK source object
The raw object is retained through the mirrored ATT&CK source bundle and object hash. The raw endpoint returns the exact object from the mirrored bundle when available.
External references and citations
MITRE external references are preserved separately from Glexia analysis so citations remain traceable to their original source records.
- [1]Microsoft SharePoint Exploit JUL 2025
Microsoft Threat Intelligence. (2025, July 22). Disrupting active exploitation of on-premises SharePoint vulnerabilities. Retrieved October 15, 2025.
Open source URL - [2]Palo Alto SharePoint Vulnerabilities JUL 2025
Unit 42. (2025, July 31). Active Exploitation of Microsoft SharePoint Vulnerabilities: Threat Brief (Updated). Retrieved October 15, 2025.
Open source URL - [3]Eye Research ToolShell JUL 2025
Eye Security. (2025, July 19). SharePoint Under Siege: ToolShell Exploit (CVE-2025-49706 & CVE-2025-49704). Retrieved October 15, 2025.
Open source URL - [4]ESET ToolShell JUL 2025
ESET Research. (2025, July 24). ToolShell: An all-you-can-eat buffet for threat actors. Retrieved October 15, 2025.
Open source URL - [5]Trend Micro SharePoint Attacks JUL 2025
Trend Micro Research. (2022, July 22). Proactive Security Insights for SharePoint Attacks (CVE-2025-53770 and CVE-2025-53771). Retrieved October 15, 2025.
Open source URL - [6]mitre-attackC0058Open source URL
Source: MITRE ATT&CK®. © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. MITRE ATT&CK and ATT&CK are registered trademarks of The MITRE Corporation. Glexia is not affiliated with or endorsed by MITRE.
