Discord security bot turns against its own users after hackers stole its identity

“The irony here is painful. A service designed to protect communities from malicious actors has become the source of a data exposure."

Share
Discord security bot turns against its own users after hackers stole its identity

A security bot designed to protect Discord communities from fake accounts and banned users was hijacked and turned against the very servers it was supposed to defend.

Double Counter is a verification service that describes itself as the "largest Discord security network", capable of blocking "alt accounts, raids and VPNs in three seconds".

On October 4, 2026, it fell victim to a "deliberate, multi-stage attack".

The attacker broke into an old server using a vulnerability in an analytics tool, before using credentials found on the machine to access cloud infrastructure and evade containment measures.

Once inside the cloud infrastructure, the attacker granted themselves administrator privileges, published links to their own Discord server, copied database records and repeatedly regained access despite attempts to lock them out.

"During the attack they took control of the bot’s Discord token, used it to post links to their own Discord server in about 50 large servers, copied part of one of our databases, and used a stolen payment key to commit financial fraud on a separate account," Double Counter wrote.

"We cut off their access, found no persistence, replaced the exposed credentials and restored the service at 19:19. We sincerely apologise to everyone affected."

The criminal spent just under six hours in the cloud, copied about 12GB of data and made $7,316 worth of fraudulent charges on a separate payment account.

"Customer funds are safe," Double Counter said.

Sowing discord

In its incident report, the verification firm said the attacker exploited a vulnerability in an analytics tool still running on a retired server, then used administrator credentials left on the machine to access Double Counter’s cloud infrastructure without creating suspicious new accounts.

Defenders tried to revoke the attacker's service-account key, but the intruder simply switched to an administrator session, re-added an SSH key and connected to the database again.

When Double Counter set a new bot token in a bid to keep the threat actor out of its systems, it was read and compromised within just two minutes.

"They then deleted backups they had created, changed the database administrator password to lock our services out and started copying the databases they could find from a cloud-hosted machine until we located and terminated their session," Double Counter said.

READ MORE: "Apple engineer" builds GitHub AI torture chamber to inflict "pain and anguish" on models

Earlier in the attack, the intruder had opened a shell inside a running bot container and read its token, using it to grant themselves administrator rights and overturn a ban on their account before posting links to their own Discord server across 50 other servers. The largest was called "Steal a Brainrot".

Using a stolen service-account key, the attacker also added their own SSH key to the cloud project and exported one of Double Counter's databases into a storage bucket.

Messages sent using the stolen token bypassed Double Counter’s systems, forcing the company to identify affected servers through user reports and the bot’s message history.

Double Counter says it has cut off the attacker, shut down the vulnerable server, revoked and replaced compromised credentials, restricted database access and introduced tighter security monitoring. An audit of 14 cloud projects found no remaining backdoors.

Doogle users, advertisers and API customers have been warned that their email addresses were exposed and should be alert to phishing attacks. Discord server administrators should delete suspicious Double Counter invitations sent on October 4 between 12:00 and 16:30 UTC and check their audit logs. Ordinary users should avoid unexpected server invitations, while anyone who failed verification during the incident should try again.

You can see the full timeline of the attack below.

TIMETYPEEVENT
FRIDAY 3 OCTOBER
04:37AttackerFirst probing of the legacy server — including a publicly reachable analytics tool on it — and of an internal API, from rotating VPN addresses.
SATURDAY 4 OCTOBER
00:47AttackerLogin to the legacy OVH server through a vulnerability in an analytics tool running on it, after working through a list of usernames.
12:03AttackerFirst use of the service-account key in our cloud.
12:08AttackerSSH key added to the cloud project.
12:19–12:35AttackerDatabase export to a bucket they created. Never downloaded.
12:26AttackerShell in a bot container. Bot token obtained.
13:24–13:34AttackerSupport server: Administrator granted by the bot (13:24), about 15 roles (13:26), staff ban (13:32), bot unban (13:33), ban again (13:34).
13:30AttackerThe bot begins posting links to the attacker’s server in large servers.
13:39ResponseWe invalidate the bot token. The bot goes offline and the attacker loses control of it.
≈14:45ResponseNew bot token installed; verifications resume by 14:49.
14:46–14:51AttackerNew shells in containers. New token exposed.
14:57ResponseReal-time monitoring of every permission the bot grants goes live.
15:04–15:09AttackerBackups deleted, database administrator password changed. Verifications stop.
15:09–15:34AttackerDatabase tables copied (about 12 GB).
15:17ResponseIntrusion identified in the cloud audit logs.
15:20ResponseService-account key disabled; database protected against deletion.
15:21ResponseAttacker’s SSH key removed from the project.
15:24ResponseDatabase closed to the internet.
15:28ResponseNew database password set; verifications resume.
≈15:34ResponseAttacker’s database-copy session located and terminated.
15:36ResponseStolen key deleted; its service account disabled and stripped of all rights.
15:54–16:46AttackerFallback to the administrator session: container shells, database connection.
≈16:08ResponseDouble Counter taken offline deliberately to cut off the fallback access.
≈16:19ResponseBot token reset and moved to our secret store.
16:25–16:52ResponseCache database migrated off the public internet onto a private network in our cloud.
17:11–17:12AttackerUsing a stolen payment key, runs fraudulent charges on a separate (Atis) payment account.
17:14ResponseAll payment-provider keys revoked and the affected account secured; the two customer charges are refunded.
17:33–17:54AttackerSSH key re-added, then five database connections. Last recorded action at 17:54:57.
≈17:55ResponseAll sessions of the administrator account revoked. The attacker’s cloud access ends.
≈18:00ResponseLegacy OVH server shut down.
18:00–18:40ResponseBackdoor audit of 14 cloud projects: nothing found. Database password replaced again (18:15).
≈18:35AttackerInvitations posted in our support server through two webhooks.
≈18:40ResponseAll ten exposed Discord webhooks deleted.
19:11–19:12ResponseLogging of every secret read enabled; alerting on sensitive cloud changes armed.
≈19:14–19:16ResponseAll session-signing keys replaced; bot token reset a final time.
19:19ResponseDouble Counter restored with new credentials.
19:40ResponseNew Discord webhooks put into service, their addresses held only in our secret store.

Trust no one, verify everything

The attack aligns with a wider trend in which hackers hijack trusted infrastructure and turn it against the people it was designed to serve, echoing a number of separate incidents in which attackers took control of ASOS's app to send push notifications to its customers, exploited Microsoft Teams to hide malicious communications and hijacked telecom routers to attack other networks.

Muhammad Yahya Patel, vCISO and cybersecurity advisor for EMEA at Huntress, told Machine: “The irony here is painful. A service specifically designed to protect Discord communities from malicious actors has become the source of one of the largest Discord-focused data exposures seen.

"A security tool becoming the source of a security breach is a reminder that trust in any platform should be proportional to how seriously it treats its own infrastructure. The nature of the data exposed creates specific downstream risks for gaming and Discord communities that are worth flagging.

READ MORE: “LLMs will be subverted”: Malware is evolving to attack AI defenders, SentinelOne warns

"Discord IDs combined with usernames and IP addresses are a useful toolkit for targeted harassment and account correlation across platforms. The immediate risk is phishing attempts referencing accurate Discord account details; users should treat any Discord-related communications with suspicion.”

In a statement, Discord said: "We’re aware of a security incident involving Double Counter, a third-party app available on Discord. While this was not a breach of Discord, we’ve disabled new installs of the app while we work with Double Counter to understand the full scope of the incident, and we’ll take further action as appropriate.”

Follow Machine