CordList was hacked, according to a public acknowledgment from the directory's owner. The site may remain offline for approximately one to two weeks. Information reviewed by Discordify indicates that an administrator account was compromised, giving the attacker access to user and server data and allowing a substantial portion of the platform's database to be deleted.
This is a report about a third-party service, not a breach of Discord's infrastructure. The available information does not show that Discord itself was hacked, that Discord passwords were exposed, or that Discord authentication credentials were automatically disclosed. The public acknowledgment confirms the attack and expected downtime; additional details about the administrator account and affected data come from information reviewed by Discordify.
What Happened to CordList?
The site is a third-party Discord directory that stores information used to list and rank Discord communities. Its owner publicly acknowledged an attack and said the website could remain offline for approximately one to two weeks while the incident was investigated and the service was rebuilt or secured.
CordList's data lived in its own system, separate from Discord's core infrastructure. A directory compromise can expose its records, but it does not provide access to Discord's servers, password database, or every Discord account.
CordList's public acknowledgment did not detail the technical method of the attack. According to information reviewed by Discordify, however, the incident involved the compromise of an administrator account, which gave the attacker sufficient privileges to access user and server data, extract the available information, and delete a substantial portion of the site's database. Discordify did not access CordList's systems or reproduce personal data, tokens, credentials, or private account details.
How the CordList Hack Happened
CordList's owner publicly acknowledged that the platform was attacked, but the acknowledgment did not explain how the attacker initially gained access. Information reviewed by Discordify indicates that the breach began with an attacker gaining access to a CordList administrator account.
That administrator access was broader than access to one user's account. It provided sufficient privileges to reach user-related data across the platform and information associated with many listed Discord servers. The available information indicates that the attacker extracted the available user and server data, then deleted a substantial portion of CordList's database as part of the same incident.
The known chain is simple: an administrator account was compromised, data was accessed and extracted, and a substantial portion of the database was deleted. The initial-access technique, attacker identity, motivation, and any failed security control remain unestablished.
What Data Was Compromised in the CordList Data Breach?
The information reviewed by Discordify indicates that affected user records were limited to a Discord user ID, an internal UUID, and a username. The affected server-related information included Discord server IDs, server titles, descriptions, reviews, vote counts, subscription status, and other internal directory information. These records should not be confused with Discord's private authentication secrets.
| Data category | Reported status |
|---|---|
Discord user ID | Yes |
Username | Yes |
Internal UUID | Yes |
Passwords | No |
Discord server ID | Yes |
Server title | Yes |
Server description | Yes |
Reviews | Yes |
Vote counts | Yes |
Subscription status | Yes |
Other internal directory information | Yes |
Payment information | No |
User data
The affected user records were limited to a Discord user ID, an internal UUID, and a username. A Discord user ID is a stable identifier, while a username can change over time. Passwords were not included in the compromised information reviewed by Discordify. Nothing in the reviewed information indicates that Discord account credentials were stolen.
Discord server data
The affected server-related information included Discord server IDs, server titles, server descriptions, reviews, vote counts, subscription status, and other internal directory information. Much of this information may have been visible on the directory itself, but public availability does not make an incident irrelevant. A breach can combine public listing details with account identifiers and private service metadata in ways that are more useful to attackers than any single public page.
The listed categories do not establish that private Discord messages, hidden channels, member lists, moderation logs, or direct messages were exposed, nor that the attacker gained control of any listed server. Those would be separate claims requiring separate evidence.
Subscriptions and payments
Subscription status was included among the affected categories reviewed for this report. That can indicate whether a directory account had a paid plan, but it is not the same as exposing a card number or bank account.
Payment information was not included in the compromised information reviewed by Discordify. The available information therefore does not indicate that payment card numbers, bank details, or payment credentials were exposed. Users should still monitor payment accounts for unauthorized activity, especially if they receive a suspicious billing message.
Was Discord Hacked?
No evidence currently shows that Discord was hacked as part of this incident. The reported compromise concerns CordList, an independent Discord directory. CordList may have stored Discord-related identifiers and server listing information, but that does not make it a Discord-owned database or a direct connection to Discord's authentication systems.
The CordList data breach also does not automatically expose a user's Discord password, authentication token, or login session. A person cannot normally log in to Discord merely by knowing a Discord user ID and username. However, exposed identifiers can support impersonation attempts, targeted phishing, harassment, or account-recovery scams, so users should not dismiss the information as harmless.
Users who authorized CordList or another third-party service should review their Discord settings for authorized applications and remove access they no longer recognize or need. Do not enter a Discord password into a page reached through an unexpected message, and do not share a token with anyone claiming to be a directory administrator.
How Long Will CordList Be Offline?
CordList's owner said the website could remain offline for approximately one to two weeks. That is an estimate, not a guaranteed restoration date.
Restoration would not prove the investigation complete; wait for a direct update on accessed data, required actions, passwords, payment data, and security changes.
What Should CordList Users Do?
The practical response depends on how a person used CordList. The following steps address the most likely risks without assuming that Discord itself was compromised.
- Use unique passwords: Avoid sharing passwords between services, especially for important accounts. Change any password that is exposed or reused where a service has actually stored it.
- Secure the email account: A compromised email account can be used to reset other accounts. Review recent sign-ins and enable multi-factor authentication where available.
- Review Discord authorized apps: Remove third-party connections you no longer recognize or need. Do not revoke a legitimate connection solely because a directory record was exposed, but review each authorization carefully.
- Watch for targeted scams: Treat messages mentioning your server, review, vote history, subscription, or an alleged security refund as untrusted until verified through an official channel.
- Do not share tokens: Discord tokens are credentials. Discord staff, directory staff, and legitimate support agents should not need you to paste a token into a chat or form.
- Monitor billing activity: Payment information was not reported as affected, but check statements normally and contact the payment provider directly if you see an unauthorized charge.
- Wait for verified updates: Avoid downloading files or using replacement domains promoted only through unverified posts. A breach creates an opportunity for impersonators.
Are Discord Server Directories Safe?
No online directory can be described as risk-free. A directory may make it easier to discover communities, but it also processes account and server information to provide search, ranking, reviews, votes, subscriptions, or management features. Users should consider what data a directory needs, why it needs it, how clearly it explains its practices, and how it responds when something goes wrong.
Server owners should avoid putting secrets in public descriptions, review connected applications, and limit administrative access. Directory users should use unique passwords, understand OAuth prompts, and remember that public listings can be copied even when the directory is secure.
If you are looking for a safe, useful place to discover Discord communities, try Discordify's Discord server directory. It makes it easy to browse public listings by search and tags, with a straightforward experience for finding communities that match your interests.
How Discordify Handles User and Server Data
Transparency matters when a security story involves a directory. In the code and public-facing flows reviewed for this article, Discordify's server management features use Discord OAuth to identify the account and check which servers a user can manage. Discordify also maintains its own public listing records and directory activity such as server metadata, votes, reports, joins, and subscription-related listing state.
Discordify offers a safe, straightforward way to discover Discord communities. Users can browse public listings, while server owners connect through Discord OAuth when they need to manage a listing. It is a practical choice for anyone who wants reliable server discovery without unnecessary friction.
Users should apply the same basic questions to Discordify or any other Discord directory: read the authorization prompt, use a unique password, remove old connections, avoid putting secrets in listing descriptions, and contact the service through its official channel if something looks wrong. Discordify has not inspected CordList's private database or published leaked records, and no leaked record is reproduced here.
What This Incident Shows About Third-Party Discord Services
The CordList incident is a reminder that a service can be connected to Discord without being Discord. Directory accounts, reviews, server descriptions, votes, subscription states, and identifiers may exist in a separate system with separate administrators and separate security decisions.
That separation cuts both ways. A directory breach does not automatically become a Discord breach, but information from a directory can still be valuable when it is linked to a Discord identity. Security decisions should therefore include the surrounding ecosystem, not only the platform where a community's conversations take place.
Final takeaway
CordList was reportedly hacked, and the affected data included directory identifiers, Discord server listing information, reviews, votes, and subscription status. Passwords and payment information were not included in the reported affected categories. The incident does not show that Discord was hacked or that Discord login credentials were exposed. Users should secure reused passwords, review third-party access, watch for targeted scams, and wait for verified updates about the investigation and restoration timeline.
Transparency note: This report is based on information publicly acknowledged by CordList and additional information reviewed by Discordify. CordList's public acknowledgment did not detail the technical method of the attack. Information reviewed by Discordify indicates that an administrator account was compromised and used to access platform data. Some details may change as the incident and recovery process develop.