Threat Actors Abused Microsoft-Signed Kernel Drivers to Disable EDR and AV
Multiple threat actors used malicious but legitimately signed Microsoft kernel drivers in targeted intrusions across telecommunications, BPO, MSSP, financial, and other sectors, according to SentinelOne. The toolkit combined the STONESTOP userland component with the POORTRY kernel driver to evade defenses by terminating, suspending, and resuming antivirus and EDR processes; later variants also added file deletion and overwrite functions. SentinelOne identified three versions of the toolkit, including two signed through Microsoft’s WHQL process, indicating that attackers were able to weaponize trusted driver signing to operate at the kernel level while undermining endpoint protections.
SentinelOne said it first reported the issue to Microsoft’s Security Response Center in October 2022 under case 75361, after which Microsoft published advisory ADV220005. The company also linked similar signed-driver abuse to a separate intrusion that ended with Hive ransomware deployment in the medical sector. Based on repeated use by distinct intruders, SentinelOne assessed with high confidence that the drivers were likely supplied through a service model, enabling multiple actors to buy or obtain signed kernel tools specifically built to neutralize security software during attacks.

Get ahead of threats like this
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
How this story unfolded
6 events from the most recent confirmed update back to the earliest known activity.
SentinelOne assesses a supplier model for malicious signed drivers
Based on its investigation, SentinelOne assessed with high confidence that different threat actors used similar malicious signed drivers likely developed and supplied as a service. The finding suggested a shared ecosystem enabling multiple intrusion sets to leverage the same defense-evasion tooling.
Separate intrusion links similar signed-driver abuse to Hive ransomware
SentinelOne linked similar abuse of signed malicious drivers to a separate intrusion in the medical sector that culminated in Hive ransomware deployment. This indicated the technique was being used across distinct operations rather than a single campaign.
Later POORTRY variant adds destructive file-handling features
A later version of the malicious signed driver toolkit added capabilities to delete and overwrite files, expanding beyond process tampering for defense evasion. SentinelOne identified three toolkit versions overall, including two signed through Microsoft's WHQL process.
Threat actors use signed POORTRY/STONESTOP toolkit in targeted intrusions
Multiple threat actors used a toolkit built around the POORTRY kernel driver and STONESTOP userland component during active intrusions against telecommunications, BPO, MSSP, financial, and other sectors. The tooling was primarily used to evade defenses by terminating, suspending, and resuming AV and EDR processes.
Microsoft publishes advisory ADV220005
After SentinelOne's disclosure, Microsoft published security advisory ADV220005 addressing the issue of malicious drivers signed through its ecosystem. The advisory marked Microsoft's formal response to the reported abuse.
SentinelOne reports malicious signed driver abuse to Microsoft
SentinelOne said it first disclosed the abuse of malicious Microsoft-signed kernel drivers to the Microsoft Security Response Center under case 75361. The disclosure concerned a toolkit including the POORTRY driver and STONESTOP component used to evade security tools during intrusions.
Related entities
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Sources
1 reference tracked. Mallory keeps watching after this page renders.
See the full picture, correlated to your attack surface.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.


