Scattered Spider's 2026 Playbook: Signed-Driver EDR Killers, Slack Surveillance, and a Sub-Hour Path to Domain Admin

Proactive Security for the AI Era
NodeZero continuously and autonomously pentests infrastructure, identity, cloud, and now web applications, chaining weaknesses across every domain the way real attackers do. Every finding ships with replayable proof showing exploitable business impact, not theoretical risk.
Scattered Spider's helpdesk-vishing playbook, calling a service desk, impersonating an employee, and talking a technician into a password or MFA reset, has been covered extensively at this point, including on this site. What gets less attention is what the group does in the hours after that initial foothold lands. Two threads of 2025-2026 reporting, IT Pro's retrospective on how the group evolved through 2025 and GuidePoint Security's "Worldwide Web" analysis of its tactics and techniques, along with CrowdStrike's own incident write-ups from the group's Q2 2025 activity, describe a post-access playbook that has changed as much as the entry technique has. This piece works through three specific pieces of that evolution: a signed-driver EDR killer that blinds endpoint defenses from inside the kernel, active monitoring of the same Slack and Teams workspaces a victim organization uses to coordinate its own response, and a privilege-escalation timeline that incident responders increasingly describe in minutes rather than days. None of this replaces the helpdesk and MFA-fatigue detail already covered elsewhere; it picks up where that detail leaves off.
Signed drivers as EDR kill switches: STONESTOP and POORTRY
Bring-your-own-vulnerable-driver (BYOVD) attacks work around a specific piece of Windows security architecture: driver signature enforcement, which is supposed to guarantee that anything running in kernel mode has been vetted and signed by a trusted authority. STONESTOP and POORTRY are a matched pair built to exploit that trust rather than break it outright. STONESTOP is the userland half: a loader and orchestrator that installs a driver and then issues it instructions about which processes to terminate. POORTRY is that driver, carrying a valid digital signature so Windows loads it without complaint, and once loaded it operates at kernel privilege, which is a higher trust level than almost any EDR agent runs at. From that position it can terminate the EDR's own processes before the EDR ever has a chance to flag the activity that follows.
This is not a new technique in the abstract; using a legitimately signed but exploitable driver to disable security tooling has been documented in ransomware-adjacent intrusions for several years, and BleepingComputer's own reporting has tracked POORTRY's evolution into what it describes as a full-featured EDR wiper rather than a narrow single-purpose tool. What matters for defenders tracking Scattered Spider specifically is that this class of tool is now a documented part of the group's post-access toolkit, not a one-off. A BYOVD kill happens after code execution is already achieved, which means it is not a substitute for preventing the initial foothold, it is what an attacker reaches for once that foothold exists and the next objective is making sure nothing watching the endpoint can report on what happens after. For the full mechanics of how BYOVD EDR killers work and the specific controls (Microsoft's vulnerable driver blocklist, Hypervisor-Protected Code Integrity) that stop them, see our dedicated BYOVD and EDR-killer defense guide, which covers the general defense pattern this specific tool pair fits into.
Watching the response: Slack and Teams as an intrusion surveillance channel
IT Pro's 2025-2026 retrospective on Scattered Spider's evolution includes a detail that is easy to read past and hard to overstate once you sit with it: the group is known to monitor communication platforms such as Microsoft Teams and Slack, impersonating compromised user accounts to facilitate further information gathering inside the target environment. The recommendation that follows from IT Pro's own reporting is direct: never share sensitive data such as passwords over these platforms, and verify identity through a video call rather than a chat message, because a chat message from a colleague's account is no longer reliable proof that the colleague sent it.
The part worth spelling out for incident responders specifically is what this means once an intrusion is already underway rather than only during initial compromise. Most organizations do not have a pre-built, out-of-band incident response communication channel sitting ready to go; when a breach is discovered, the instinct is to spin up a new channel or thread in the same Slack or Teams tenant the organization already uses every day, because that is the tool everyone already has open. If Scattered Spider has a compromised account with visibility into that tenant, an incident response channel created inside it is not a safe room, it is a window. This is an inference from the documented monitoring behavior rather than a claim that any specific responding team has been directly observed this way, but it is the reason the standard incident response guidance to move coordination to an out-of-band channel, a separate platform, a different tenant, a phone bridge, matters more against this specific actor than it does against most.
Briefings like this, every morning before 9am.
Threat intel, active CVEs, and campaign alerts, distilled for practitioners. 50,000+ subscribers. No noise.
The compressed timeline from access to domain admin
One figure that has circulated in 2025-2026 discussion of Scattered Spider intrusions is a time-to-domain-admin as short as roughly 40 minutes in an individual documented case. We were not able to independently verify a specific named primary source tying that exact number to a specific incident within the scope of this article's research, and readers should treat it as a widely repeated figure rather than a confirmed, sourced benchmark until it can be traced to a specific vendor's incident report.
What is directly verifiable is the broader shape of the trend that figure is meant to illustrate. CrowdStrike's own mid-2025 write-up on Scattered Spider's escalating activity across industries describes the group deploying Active Directory reconnaissance tooling, specifically ADExplorer and ADRecon.ps1, early in the intrusion lifecycle, alongside a toolkit built for speed: tunneling utilities and remote access software that let an operator move rather than dwell. A group that reaches for AD enumeration tooling within the same operational window as initial access, rather than treating reconnaissance as a separate, patient phase, is consistent with a privilege-escalation timeline measured in minutes to a few hours, not the multi-day-to-multi-week dwell times that characterized ransomware intrusions several years ago. Faster initial access techniques compound this further: the same MFA-fatigue and number-matching-bypass approaches covered in our MFA prompt-bombing defense guide can hand an attacker a valid, already-authenticated session in minutes, which removes one of the slowest steps from what used to be a longer chain.
An expanded toolkit built for tunneling and speed
The tools Scattered Spider reaches for once inside an environment have also broadened. CrowdStrike's incident reporting from the group's Q2 2025 activity, including targeting in the aviation, insurance, and retail sectors, documents a toolkit heavy on tunneling and remote access: Chisel configured to communicate through trycloudflare.com subdomains, ngrok, Pinggy, Rsocx, and Teleport for establishing covert command-and-control channels that ride on legitimate cloud infrastructure, alongside MobaXterm and S3 Browser for interacting with remote systems and cloud storage, and the abuse of legitimate remote access tools like TeamViewer and AnyDesk to blend administrative access into normal-looking traffic.
GuidePoint Security's "Worldwide Web" analysis adds a credential-theft dimension to the same picture: tooling built specifically to target privileged access management platforms, including CyberArk and Thycotic Secret Server, alongside a documented pattern of vishing calls using American-accented speakers to social-engineer password resets, and Windows registry modification scripts used for defense evasion once inside. GuidePoint's research also ties a RansomHub affiliate with prior ALPHV/BlackCat operational history to Scattered Spider activity, consistent with a group that operates as much through affiliate relationships and shared tooling as it does through a single fixed crew. None of these tools are individually new to the threat landscape; what is notable is how many of them show up together inside a single Scattered Spider intrusion chain, favoring infrastructure that rides on trusted cloud domains (Cloudflare, ngrok) specifically because that traffic pattern is harder to distinguish from legitimate business use than a custom C2 protocol would be.
A defensive framework for the current playbook
Point defenses against any one of these techniques help, but the group's effectiveness comes from how the pieces stack: fast initial access, immediate visibility into the target's own response coordination, and tooling designed to disable the controls that would otherwise catch the escalation. A framework that addresses the stack looks like this.
Enforce the Microsoft vulnerable driver blocklist and HVCI
STONESTOP and POORTRY only work if the target endpoint will load a signed-but-exploitable driver. Microsoft's vulnerable driver blocklist, kept current and enforced, combined with Hypervisor-Protected Code Integrity where hardware supports it, closes the specific loading path this tool pair depends on. See the [BYOVD and EDR-killer defense guide](/blog/byovd-edr-killer-defense-guide) for the full configuration detail.
Move incident response coordination off the daily-use collaboration tenant
Maintain a pre-established, out-of-band channel for incident response, a separate platform, a distinct tenant, or a phone bridge, rather than improvising a new Teams or Slack channel inside the same tenant an intruder may already be watching. Decide this before an incident, not during one.
Monitor for tunneling traffic riding on trusted cloud domains
Chisel over Cloudflare tunnel subdomains, ngrok, and Pinggy are hard to distinguish from legitimate SaaS traffic at the DNS layer alone. Egress monitoring that flags new or unusual outbound connections to these specific services, correlated with endpoint process activity, catches what domain reputation filtering alone will miss.
Harden and monitor privileged access management platforms directly
GuidePoint's research documents tooling aimed specifically at CyberArk and Thycotic Secret Server. Treat PAM platform access logs and vault-retrieval events as a first-class detection surface, not just a credential store to configure once and leave alone.
Rebuild alerting and containment SLAs around a sub-hour attacker timeline
If AD reconnaissance and privilege escalation can begin within the same operational window as initial access, an alerting pipeline with a multi-hour triage backlog is effectively undefended against this actor. Validate that your mean time to detect and contain a privileged-access anomaly is measured in minutes, and treat any gap against that target as the priority finding from this framework, ahead of any single tool acquisition.
The bottom line
Scattered Spider's helpdesk-vishing entry technique and MFA-fatigue tactics are well covered ground at this point. What has changed for 2025-2026 is everything that happens next: STONESTOP and POORTRY give the group a way to blind EDR at the kernel level using a signed driver rather than trying to evade detection at the process layer, IT Pro's reporting confirms the group actively monitors Slack and Teams for operational intelligence during an intrusion, which is a direct risk to any incident response coordinated inside the same tenant, and CrowdStrike's incident data shows Active Directory reconnaissance tooling deployed early enough to be consistent with a privilege-escalation timeline measured in minutes to hours rather than days. The specific 40-minute figure attached to that last point remains unverified against a named primary source in our research and should be treated as illustrative rather than confirmed. The direction it illustrates is not in question. Defenses built around a multi-day detection window, a shared incident-response Slack channel, and endpoint agents with no driver-blocklist enforcement are built for the group Scattered Spider used to be, not the one operating now.
Frequently asked questions
What is Scattered Spider's current attack playbook in 2026?
Beyond its established helpdesk-vishing entry technique, Scattered Spider's 2025-2026 operations layer in BYOVD-based EDR killer tooling to disable endpoint defenses after access, active monitoring of victim Slack and Teams workspaces for operational awareness during the intrusion, an expanded toolkit of tunneling and remote-access utilities to move data and maintain access, and a privilege-escalation timeline that incident responders describe as far faster than the group's earlier campaigns.
What are STONESTOP and POORTRY, and how does Scattered Spider use them?
STONESTOP is a Windows userland utility that acts as a loader and orchestrator: it installs a malicious kernel driver and instructs it which processes to terminate. POORTRY is that driver, digitally signed so it loads despite Windows driver signature enforcement, and it terminates security software such as EDR agents at the kernel level. Together they are a bring-your-own-vulnerable-driver (BYOVD) EDR killer pair, letting an attacker blind endpoint defenses from inside the operating system rather than trying to evade them at the process level.
Does Scattered Spider really monitor victim Slack and Teams during an active intrusion?
According to IT Pro's 2025-2026 reporting, yes: Scattered Spider is known to monitor communication platforms such as Microsoft Teams and Slack, impersonating compromised user accounts to facilitate further information gathering inside a target environment. This is a meaningful operational security risk for defenders specifically because many organizations coordinate their own incident response over the same Teams or Slack tenant the attacker may already have a foothold in, so IT Pro's guidance to never share credentials over these platforms and to verify identity over video applies just as much mid-incident as it does day to day.
How fast can Scattered Spider reach domain admin access after initial compromise?
A specific figure of roughly 40 minutes has circulated in 2025-2026 incident response commentary on individual Scattered Spider intrusions, but we could not independently verify a single named primary source tying that exact number to a specific documented case within this article's research. What is verifiable is the broader trend: CrowdStrike's mid-2025 incident write-ups describe Active Directory reconnaissance tools like ADExplorer and ADRecon.ps1 being deployed early in the intrusion lifecycle, consistent with a privilege-escalation timeline measured in minutes to a few hours rather than the multi-day dwell times seen in earlier Scattered Spider campaigns. Treat the 40-minute figure as illustrative of that direction rather than a confirmed universal benchmark.
How does this differ from Scattered Spider's helpdesk social engineering and MFA prompt-bombing tactics?
Helpdesk social engineering and MFA prompt bombing describe how Scattered Spider gets its initial foothold, tricking a service desk into resetting credentials or exhausting a victim's patience with repeated push notifications until one is approved. This article covers what the group does after that foothold is established: killing EDR at the kernel level, watching the victim's own communications for operational awareness, and moving to domain-level privilege faster than most environments are built to detect and contain. For the entry-technique detail, see our guides on [MFA prompt-bombing defense with number matching and FIDO2](/blog/mfa-prompt-bombing-fatigue-attack-defense-number-matching-fido2) and [helpdesk identity verification hardening against Scattered Spider](/blog/helpdesk-social-engineering-identity-verification-scattered-spider).
What should security teams change given this evolved Scattered Spider playbook?
Three changes matter most. First, harden against BYOVD specifically, since a vulnerable-driver EDR killer defeats endpoint detection regardless of how strong the endpoint agent itself is; our [BYOVD and EDR-killer defense guide](/blog/byovd-edr-killer-defense-guide) covers the Microsoft vulnerable driver blocklist and HVCI controls that stop POORTRY-class tools from loading. Second, move incident response coordination to a channel and tenant separate from the organization's daily-use Slack or Teams workspace, since that is exactly where Scattered Spider has been reported monitoring for operational intelligence. Third, assume detection and containment windows are now measured in tens of minutes to a few hours rather than days, and validate that alerting-to-containment time actually matches that assumption rather than a slower target set years ago.
Sources & references
- IT Pro, Scattered Spider evolved massively in 2025, here's what to expect in 2026
- GuidePoint Security, Worldwide Web: An Analysis of Tactics and Techniques Attributed to Scattered Spider
- CrowdStrike, SCATTERED SPIDER Escalates Attacks Across Industries
- BleepingComputer, PoorTry Windows driver evolves into a full-featured EDR wiper
Free resources
Critical CVE Reference Card 2025–2026
25 actively exploited vulnerabilities with CVSS scores, exploit status, and patch availability. Print it, pin it, share it with your SOC team.
Ransomware Incident Response Playbook
Step-by-step 24-hour IR checklist covering detection, containment, eradication, and recovery. Built for SOC teams, IR leads, and CISOs.
Get threat intel before your inbox does.
50,000+ security professionals read Decryption Digest for early warnings on zero-days, ransomware, and nation-state campaigns. Free, daily, no spam.
Unsubscribe anytime. We never sell your data.

Founder & Cybersecurity Evangelist, Decryption Digest
Cybersecurity professional with expertise in threat intelligence, vulnerability research, and enterprise security. Covers zero-days, ransomware, and nation-state operations for 50,000+ security professionals every morning.
