Skip to content

Security Widely confirmed8 publishers 3 min read Published Updated

Investigators sinkholed Sality's peer list to strand more than 15,000 infected Windows hosts

The August 31 operation cut the operator off from over 15,000 bots without cleaning a single disk. The Sality hosts on your network will stop calling home and keep infecting every executable they can write to.

The Watch · Security desk

Send a correction

What happened

  • Authorities in the U.S., Bulgaria, Hungary and Romania seized Sality-linked domains on August 31, 2026, while CrowdStrike and the Shadowserver Foundation ran a peer-to-peer sinkhole against the botnet.
  • The sinkhole took over Sality's known super peers, purging infected machines' peer lists and cutting off both direct payload transfers and payload download instructions.
  • Two independent networks, version 3 and version 4, were still live at the time; CrowdStrike says they shared a codebase and an operator but ran incompatible protocols and different cryptographic keys.
  • EggJagger, a clipboard hijacker that swaps cryptocurrency wallet addresses for the operator's own, has been the main payload for eight years and is estimated to have taken at least $150,000.

Why it matters

  • Who's exposed exposure The disks themselves were never touched. Infected hosts keep writing themselves into executables and travelling on shares and USB media, so a machine that goes quiet after August 31 is still a source inside the perimeter.
  • What's now possible capability Peer list manipulation has now landed on GameOver Zeus, Kelihos and Sality, which retires the assumption that an unauthenticated P2P protocol buys resilience against a coordinated takedown.
  • Who has to decide decision Hunting has to shift from callback detection to executable integrity, because the traffic that used to expose Sality is exactly what the sinkhole removed.
  • What it costs cost At roughly $10 stolen per infected machine, funding this disruption never made business sense for any single victim organisation, so the removal work now lands on more than 15,000 unrelated owners.

Sality accepted anyone. A bot added any machine that was publicly reachable and answered the P2P handshake correctly, without authenticating itself, presenting any cryptographic identity, or being checked against an allowlist [7]. That is what the operation used: reachable nodes get accepted as peers, then a poisoned peer list propagates until the operator's real super peers are gone from every bot's address book [4]. The same peer list manipulation worked against GameOver Zeus in 2014 and Kelihos in 2017 [6].

The operator cannot answer this in software. Sality has no code update channel; it spreads as a file infector that attaches itself to executables on disk, which is why CrowdStrike says the protocol cannot be patched [17]. Pushing an authenticated version 5 to hosts already running the incompatible version 3 and version 4 protocols that were live at the time of the disruption is not possible [15]. CrowdStrike says the botnet is no longer under the operator's control [11].

The yield explains two decades of neglect. At least $150,000 taken through clipboard substitution [8], spread across the eight years EggJagger has been the primary payload [9], works out to roughly $18,750 a year [20]; divided across more than 15,000 infected machines [5] it is about $10 per victim host [19]. At that rate, funding a takedown never made business sense for any single victim.

The worm survives the sinkhole. Sality spread through infected network shares, USB devices, file sharing, compromised websites and email attachments, regenerating infections with no active effort from the operator [12]. That mechanism is untouched. A host infected next month will still write itself into every executable it can reach; it just will not receive EggJagger. For defenders the usual signal inverts: after August 31 the network chatter stops while the disk problem stays, so any infection inventory built from C2 callbacks will undercount. Dragos documented in July 2022 that Sality had reached industrial engineers and operators and pulled PLCs into the botnet [21], so OT asset owners do not get to file this as a desktop cleanup.

What is public is the seizure of Sality-linked domains in the U.S. and Europe [2] and the sinkhole itself, run with Europol and Eurojust support [3]. Attribution to a group tracked as SALTY SPIDER, likely operating out of the Republic of Bashkortostan in Russia, is CrowdStrike's assessment and is single-sourced here [13]. The reason the identification matters is history: CrowdStrike ties the same operator to DDoS campaigns against forex2030[.]com in April 2016, kharkovforum[.]com a day after Russia's full-scale invasion of Ukraine in February 2022, and AvanChange in September 2023 [14]. A clipper botnet that gets repointed at a Ukrainian forum inside 24 hours has a second use.

Joint disruptions have been common this year, and this one joins the list: the takedown of SocksEscort and the Aisuru, KimWolf, JackSkid and Mossad C2 infrastructure in March, and Dutch authorities taking a 17-million-device botnet offline in May [22].

What to watch

  • Whether Shadowserver publishes country- or ASN-level sinkhole telemetry, which is the only reliable count of hosts still carrying the infector.
  • Whether a second operator recruits the orphaned version 3 and version 4 peers, since the same unauthenticated handshake admits anyone who can stand up reachable nodes.
  • Charges or arrests in Bulgaria, Hungary or Romania, which would move this from infrastructure disruption to prosecution.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence72
Adoption
Not scored
Hype gap+25
Incentives68
Confidence75

Perspective Coverage

8 publishers
Builder
Builder 36%
Operator
Operator 42%
Investor
Investor 22%
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    The U.S. Department of Justice announced the takedown of the Sality P2P botnet; the operation was undertaken on August 31, 2026 by authorities from the U.S., Bulgaria, Hungary and Romania in collaboration with CrowdStrike and the Shadowserver Foundation, including a peer-to-peer sinkhole operation and seizure of Sality-linked domains in the U.S. and Europe.

    Reported Supported Source: U.S. Department of Justice, via The Hacker NewsView cited source
  2. [2]

    The DOJ, FBI and DCIS seized Sality-linked domains in the United States, while law enforcement partners in Bulgaria, Hungary and Romania seized additional Sality-linked domains hosted in Europe.

    Reported SupportedView cited source
  3. [3]

    The disruption was carried out with the DOJ, FBI, DCIS and the Shadowserver Foundation, with support from Europol, Eurojust and law enforcement agencies in Bulgaria, Hungary and Romania.

    Reported Supported Source: CrowdStrikeView cited source
  4. [4]

    The botnet was disrupted by sinkholing Sality's list of known super peers, which form its communication backbone, to block file packs (direct payload transfers) and URL packs (payload download instructions) from propagating and to purge infected machines' peer lists.

    Reported Supported Source: CrowdStrikeView cited source
  5. [5]

    The botnet enabled the operator to distribute malicious payloads to over 15,000 infected machines worldwide.

    Reported Supported Source: CrowdStrikeView cited source
  6. [6]

    The counterattack used peer list manipulation, an approach also used in the 2014 GameOver Zeus and 2017 Kelihos botnet disruptions, and leveraged the fact that Sality bots blindly trusted the P2P network without verifying who was added to it.

    Reported SupportedView cited source
  7. [7]

    As long as a machine was publicly reachable and responded correctly to the P2P handshake it was accepted as a legitimate peer; Sality had no authentication, cryptographic identity or allowlist, so anyone could join the network.

    Reported Supported Source: CrowdStrikeView cited source
  8. [8]

    EggJagger, a clipper or clipjacking tool, monitors the clipboard for cryptocurrency wallet addresses and substitutes attacker-controlled ones; the threat actors are estimated to have stolen at least $150,000 using this method.

    Reported SupportedView cited source
  9. [9]

    For the past eight years the primary Sality payload has been EggJagger.

    Reported Supported Source: CrowdStrikeView cited source
  10. [10]

    Sality has been documented in the wild since 2003 and infects and modifies Windows executable files, spreading additional malware for credential theft, spam distribution, proxy services, network exploitation and DDoS.

    Reported SupportedView cited source
  11. [11]

    CrowdStrike says the Sality botnet is now no longer under the operator's control following the disruption.

    Reported Supported Source: CrowdStrikeView cited source
  12. [12]

    Sality has been distributed through infected network shares, USB devices, file sharing, compromised websites, email attachments and P2P networks, creating a self-propagating botnet that regenerates new infections without any active effort from the threat actor.

    Reported SupportedView cited source
  13. [13]

    CrowdStrike says Sality is controlled by a criminal group it tracks as SALTY SPIDER, likely operating out of the Republic of Bashkortostan in Russia.

    Reported Supported Source: CrowdStrikeView cited source
  14. [14]

    CrowdStrike says Sality was used in three notable DDoS campaigns: against the Arabic Financial Forum (forex2030[.]com) in April 2016, a Ukrainian forum (kharkovforum[.]com) in February 2022, a day after Russia's full-scale invasion of Ukraine, and AvanChange in September 2023.

    Reported Supported Source: CrowdStrikeView cited source
  15. [15]

    Two independent Sality P2P networks, known as version 3 and version 4, remained active until the disruption; CrowdStrike says they shared the same codebase and operator but used incompatible protocol versions and different cryptographic keys.

    Reported Supported Source: CrowdStrike Counter Adversary OperationsView cited source
  16. [16]

    First Assistant United States Attorney Bill Essayli said the takedown shows that by working together the public and private sectors can be a powerful force for good.

    Reported Supported Source: Bill Essayli, First Assistant U.S. Attorney
  17. [17]

    CrowdStrike says Sality's P2P protocol cannot be patched because, unlike conventional malware that receives code updates from a C2 server, Sality's spreading mechanism is a file infector that propagates by attaching itself to executables on disk.

    Reported Supported Source: CrowdStrikeView cited source
  18. [18]

    Sality had been operating for 23 years at the time of the disruption.

    Derived Supported
  19. [19]

    EggJagger theft amounts to roughly $10 per infected machine.

    Derived Supported
  20. [20]

    EggJagger theft averages roughly $18,750 per year over the eight years it has been the primary payload.

    Derived Supported
  21. [21]

    In July 2022 Dragos revealed a campaign that targeted industrial engineers and operators to seize control of programmable logic controllers and co-opt those devices into the Sality botnet.

    Reported Supported Source: DragosView cited source
  22. [22]

    In March, American and European authorities with private partners disrupted the SocksEscort proxy network and took down C2 infrastructure used by the Aisuru, KimWolf, JackSkid and Mossad botnets; in May Dutch authorities took a botnet of 17 million devices offline.

    Reported SupportedView cited source

Sources

8 independent publishers whose own reporting we read for this story.

  1. bleepingcomputer.com

    1 article · September 2, 2026

    Sality botnet infrastructure dismantled in joint global takedown
  2. Peer Pressure: Inside the Sality Botnet Disruption Operation
  3. cyberscoop.com

    1 article · September 2, 2026

    Dogged Russia-based botnet dismantled after 23-year run
  4. helpnetsecurity.com

    1 article · September 2, 2026

    Global sinkhole operation ends Sality botnet’s 23-year run
  5. infosecurity-magazine.com

    1 article · September 3, 2026

    International Operation Disrupts Sality P2P Botnet
  6. securityweek.com

    1 article · September 2, 2026

    23-Year-Old Sality P2P Botnet Disrupted
  7. thehackernews.com

    1 article · September 1, 2026

    Authorities Turn Sality's P2P Network Against Itself, Cutting Off New Malware Payloads
  8. therecord.media

    1 article · September 2, 2026

    Sality, one of the longest-running botnets, finally gets disrupted

Topics and entities

Topics