Double Counter Discord protection service breached via Metabase flaw; 275k emails and usernames leaked
In October 2026, the Discord server protection service Double Counter suffered a data breach attributed to a vulnerability in the Metabase analytics tool. The company's disclosure notice states that attackers accessed a subset of its data. That data was later published publicly and contains about 275k unique email addresses and Discord usernames. Have I Been Pwned added the corpus on 7 Oct 2026, with 274.9k affected addresses. A small number of records belonging to paying subscribers, whose purchases were processed via Stripe, also include names, countries and postcodes.
Detalhes técnicos
- Root cause is reported as an unspecified vulnerability in Metabase. The article gives no CVE identifier or exploitation details.
- Exposed data: email addresses, Discord usernames, and for a small number of paying subscribers, names, countries and postcodes.
- The data was published publicly after the intrusion. The attacker is not identified.
Remediação
- Affected users should change any password reused with the affected accounts and enable 2FA where supported.
- Use a password manager to keep passwords unique.
- Organizations running Metabase should apply vendor security updates and avoid exposing the tool directly to the internet.
Linha do tempo
-
Double Counter Discord protection service breached via Metabase flaw; 275k emails and usernames leaked
ler a análise desta fonte ocultar
In October 2026, the Discord server protection service Double Counter suffered a data breach attributed to a vulnerability in the Metabase analytics tool. The company's disclosure notice states that attackers accessed a subset of its data. That data was later published publicly and contains about 275k unique email addresses and Discord usernames. Have I Been Pwned added the corpus on 7 Oct 2026, with 274.9k affected addresses. A small number of records belonging to paying subscribers, whose purchases were processed via Stripe, also include names, countries and postcodes.
Technical Details
- Root cause is reported as an unspecified vulnerability in Metabase. The article gives no CVE identifier or exploitation details.
- Exposed data: email addresses, Discord usernames, and for a small number of paying subscribers, names, countries and postcodes.
- The data was published publicly after the intrusion. The attacker is not identified.
Remediation
- Affected users should change any password reused with the affected accounts and enable 2FA where supported.
- Use a password manager to keep passwords unique.
- Organizations running Metabase should apply vendor security updates and avoid exposing the tool directly to the internet.