MyRecon OSINTDouble Counter
A server safeguard. An exposed analytics tool.
Double Counter helps protect Discord servers. Its breach account points to a vulnerability in Metabase, an analytics tool. The published data connected email addresses with Discord usernames.
Follow the story
On 4 October 2026, Double Counter was breached. 274,922 accounts were exposed, including email addresses, geographic locations, names. MyRecon rates it 39/100, moderate.
How the story unfolded
Open a step to read the detail. Missing dates stay unknown.
02Entry point
In October 2026, the Discord server protection service Double Counter suffered a data breach attributed to a vulnerability in the Metabase analytics tool .
03Discovery and disclosure
A separate discovery or company-disclosure date is not established by this feed record.
04Added to the breach catalogue
2026-10-07. This is the catalogue date, not necessarily the disclosure date.
05Reported outcome
274,922 accounts are listed in this breach. This is a count of accounts, not necessarily individual people. The reported exposed data includes Email addresses, Geographic locations, Names, Usernames.
How a Discord handle became an email trail
The important connection is between an account and its contact details. A message using your Discord handle may feel familiar; that familiarity is not proof that the sender is legitimate.
In October 2026, the Discord server protection service Double Counter suffered a data breach attributed to a vulnerability in the Metabase analytics tool . In its disclosure notice, Double Counter advised that attackers gained access to a subset of its data. A corpus of data was subsequently published publicly and contained 275k unique email addresses and Discord usernames.
A small number of records belonging to paying subscribers whose purchases were processed via Stripe were also present and included names, countries and postcodes.
Breach description from Have I Been Pwned, used under a CC BY 4.0 licence.
Read the original disclosure ↗
01 / The reported entry point
In October 2026, the Discord server protection service Double Counter suffered a data breach attributed to a vulnerability in the Metabase analytics tool .
02 / What the record does not tell us
The published account does not establish the motive. We cannot tell what the attackers intended from the exposed data alone.
Reported demands or attempts to sell data describe what happened, rather than prove every attacker's intention.
03 / What left the service
274,922 accounts are listed in this breach. This is a count of accounts, not necessarily individual people.
The reported exposed data includes Email addresses, Geographic locations, Names, Usernames.
What was exposed, and why it matters
Email addresses
An exposed address can be used for targeted phishing. A familiar service name does not make a message trustworthy.
Geographic locations
The account describes countries and postcodes for a small subset of paying subscribers. It does not establish precise or live locations.
Names
Names appeared in a small subset of subscriber records and may make a fraudulent message more convincing.
Usernames
Discord usernames can provide leads to other public profiles. A matching handle alone does not prove shared ownership.
What to do if you were in it
Questions people ask about this breach
Was my email address in the Double Counter breach?
Use the email box on this page. The result applies only to this incident. If the provider does not cover this breach, we say so. A missing match does not prove you were unaffected.
What data was leaked in the Double Counter breach?
email addresses, geographic locations, names, usernames. Each one is explained above, along with what it means for the person it belongs to.
When did it happen, and when did it become public?
The breach is dated 4 October 2026. It was published to Have I Been Pwned on 7 October 2026, a gap of 3 days during which the data was already out.
Is the Double Counter breach real?
Yes. Have I Been Pwned lists it as verified, meaning the data was checked against the source rather than taken on trust.
How many people were affected?
274,922 accounts. That is accounts rather than people, one person often has several.
Read next
Also in the archive
Case Files: how the landmark breaches actually happened →
Three kinds of content appear on this page and they are kept apart deliberately. The breach description is quoted from Have I Been Pwned under its licence. The severity score, the field-by-field explanation and the advice are computed from the record itself, every sentence derives from a number or a flag in it, which is what stops the analysis drifting from the evidence. Anything under the "MyRecon's take" byline is editorial: our reading of this breach, presented as opinion rather than as a finding.