Warlock’s SharePoint campaign and the operational stakes
A ransomware intrusion can spread from an exposed collaboration server to other machines on an organization’s network. BleepingComputer reports that Warlock targeted a water utility, a telecommunications provider, a regional government body and a university by exploiting vulnerabilities in on-premises Microsoft SharePoint.
Published October 2, 2026, the report draws on research from Symantec and Carbon Black. Researchers describe an initial-access sequence involving SharePoint vulnerabilities, followed by placement of a web shell designed to work across multiple SharePoint versions. The report does not identify all four victims or give a complete timeline for each, so the findings do not offer a full account of every victim’s response.
The reported victims span water, telecommunications, regional public administration and higher education. BleepingComputer reports no service disruption or operational-technology impacts. The broader concern—that a vulnerable enterprise server can put an organization at risk—is an inference from the reported activity, not a documented impact on these victims.
SharePoint vulnerabilities and distinct attributions
BleepingComputer reports that Warlock emerged in June 2025 and drew attention the following month after exploiting a chain of zero-day vulnerabilities in Microsoft SharePoint known as ToolShell. The identifiers are CVE-2025-49704, CVE-2025-49706, CVE-2025-53770 and CVE-2025-53771. Microsoft observed state-backed groups Linen Typhoon and Violet Typhoon using ToolShell exploits by August, alongside a ransomware actor Microsoft tracks as Storm-2603, according to the report.
The report distinguishes these attributions. Symantec identifies the actor it tracks as Longlegs as the same actor behind Warlock ransomware; Microsoft’s Storm-2603 designation is reported separately. The findings do not establish that all the named groups are the same entity.
ToolShell and other SharePoint flaws remained viable more than a year after Warlock first emerged exploiting SharePoint weaknesses, the report notes. For defenders, that persistence highlights the risk of exposed or unremediated servers as routes into an organization. It does not establish that any particular victim had an unpatched system.
Inside one reported intrusion
Researchers examined an intrusion that began on July 22. Two days after initial access, the actor conducted reconnaissance and deleted what appeared to be staging artifacts. This is one observed intrusion, not a definitive sequence for every Warlock incident.
The attacker placed a ransomware payload in the domain’s SYSVOL share, which stores public files and replicates them across domain controllers. Researchers describe this as a known way to distribute a payload for execution through a logon script or Group Policy object, rather than handling hosts individually.
The campaign also involved administrative capabilities that supported remote access and execution. The main executable for Visual Studio Code Insiders was installed as a service, enabling remote connections to compromised machines through VS Code’s built-in tunneling capability. Researchers found NetExec, an open-source penetration-testing framework, on one system; according to the report, it supported Active Directory enumeration, credential spraying and remote command execution.
The observed activity extended beyond encryption to discovery, remote access and domain-wide payload distribution. That sequence suggests defenders should look for signs of compromise before a ransom note or encrypted files appear.
Defense disabling preceded rapid encryption
In the July 22 intrusion, the threat actor deployed a tool that disabled security protection on at least 40 hosts within about two hours. Researchers reported that Warlock ransomware was then launched on at least 33 hosts. In a separate incident on July 31, ransomware appeared almost as soon as defenses were disabled on each host after deployment of the protection-disabling tool.
The report describes an antivirus and endpoint-detection-and-response (AV/EDR) killing tool delivered through the bring-your-own-vulnerable-driver technique, or BYOVD. In attacks attributed to Longlegs, researchers say the tool used a signed K7RKScan driver vulnerable to CVE-2025-1055. This flaw is separate from the four SharePoint ToolShell identifiers: the report associates it with disabling endpoint protections after access, not with initial SharePoint entry.
For incident review, the distinction matters: SharePoint exploitation is described as the initial-access method, while use of a vulnerable signed driver appears later in the defense-evasion sequence in some attacks. The report does not establish that every victim encountered the same driver activity or that hosts were affected uniformly.
What security teams should take from the findings
Organizations running on-premises SharePoint should determine whether their systems are exposed and whether relevant security updates and mitigations have been applied. This recommendation follows from the reported use of SharePoint vulnerabilities for initial access and their continued viability; it is defensive guidance, not an action attributed to the researchers.
Defensive reviews can extend beyond the web server to look for unexpected web shells, unusual service installations, VS Code Insiders tunneling, suspicious SYSVOL activity, and logon scripts or Group Policy used to distribute executables. Review NetExec or similar enumeration and remote-execution activity in context, particularly alongside credential spraying or unusual Active Directory discovery. None of these behaviors alone proves Warlock activity.
The reported progression—from disabling protection on dozens of hosts to executing ransomware, supports reviewing whether tamper protection, security telemetry and escalation paths remain effective when an attacker tries to interfere with them. If a vulnerable driver may be involved, assess driver-control policies and investigate unexpected signed-driver activity. Researchers specifically name K7RKScan and CVE-2025-1055 in some attacks attributed to Longlegs, but the report does not indicate that every victim encountered the driver. These are response recommendations based on the reported behavior.
Preserve evidence while prioritizing containment and safe restoration. In the observed intrusion, the actor deleted what appeared to be staging artifacts during reconnaissance. Symantec and Carbon Black also published indicators of compromise for files and infrastructure; consult their report for the exact values, which are not reproduced here.
warlocks sharepoint campaign and the operational stakes
warlocks sharepoint campaign and the operational stakes