Loading malware…
Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.
9 distinct techniques documented for this family, organized by ATT&CK tactic.
Policy-based QoS (Quality of Service) allows you to set an absolute outbound bandwidth limit (throttling rate) for specific applications, ports, or protocols in Windows... EDRChoker... creates QoS policies that limit those processes to 8 bits per second.
Modern EDR platforms rely on a persistent, low-latency connection between the endpoint agent and a cloud-based management server. Sever that connection and the EDR agent effectively goes dark, unable to report detections, receive updated policies, or accept remote commands from administrators.
Threat actors with elevated privileges on the asset can point a QoS policy at an EDR agent and set the rate to effectively zero, limiting the capability of the agent to generate telemetry in the cloud console. | The technique is different compared to the EDR Silencing because packets are not dropped but limited due to the very low bandwidth.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A proof-of-concept tool that abuses Windows QoS policies to throttle outbound bandwidth for EDR agent processes, disrupting telemetry to cloud consoles without dropping packets.
A tool or malware referred to as EDRChoker that interferes with EDR telemetry by throttling agent bandwidth via Policy-based QoS, causing agent communications to time out and effectively blocking defenses.
Match every observed IP, domain, and hash against your live telemetry.
Named campaigns wielding this family, with evidence pinned to each claim.
CVEs this family uses for access and lateral movement.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Every documented technique, ranked by evidence weight.
Reddit, Mastodon, and CTI community discussion around this family.