Discord Data Breach Involving Compromised Government ID Photos and Third-Party Denial
Discord experienced a significant data breach that resulted in the exposure of approximately 70,000 users' government-issued identification photos, including driver's licenses and passports submitted for age verification. The breach was initially disclosed by Discord, which stated that a 'small number' of government IDs had been compromised, later clarifying that the number was around 70,000. Discord attributed the breach to a third-party customer service support firm, 5CA, which it contracts for customer support operations. However, 5CA publicly refuted these claims, asserting that none of its systems were involved in the breach and that it had not handled government-issued IDs for Discord. 5CA emphasized that its platforms and systems remained secure, with all client data protected under strict security controls, and that there was no evidence of impact on other clients or systems. The company also stated that access controls, encryption, and monitoring systems were fully operational and had been placed under heightened review as a precaution. 5CA attributed the incident to 'human error' but did not provide further details on the nature of this error. Media reports and statements from 5CA suggest that the breach occurred outside of its infrastructure. Hackers claiming responsibility for the breach told BleepingComputer that they accessed Discord's Zendesk account for 58 hours on September 20, allegedly using compromised credentials belonging to a support agent from a third-party company. This suggests that the attack vector may have involved credential compromise rather than a direct hack of 5CA's systems. Discord has not yet confirmed which company was responsible for holding the compromised government ID photos. The incident has raised concerns about the security of third-party vendors and the handling of sensitive user data. Both Discord and 5CA have faced scrutiny over their security practices and communication regarding the breach. The lack of clarity about the exact cause and responsible party has left users and the cybersecurity community seeking more information. The breach underscores the risks associated with outsourcing customer support functions and the importance of robust access controls and monitoring. Discord's response included updating its public statements and working to clarify the scope and impact of the breach. 5CA's denial and emphasis on its security posture highlight the challenges in attributing responsibility in incidents involving multiple vendors. The incident remains under investigation, with both companies maintaining that their systems were not directly compromised. The exposure of sensitive government ID photos has significant privacy implications for affected users. Ongoing reviews and heightened security measures have been implemented by 5CA as a precaution. The breach serves as a reminder of the persistent threat posed by compromised credentials and the need for continuous vigilance in third-party risk management.

Get ahead of threats like this
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
How this story unfolded
7 events from the most recent confirmed update back to the earliest known activity.
Suspected SLH involvement is denied
Scattered Lapsus$ Hunters was initially suspected in the incident, but the group denied involvement. Reporting indicated the perpetrators may instead belong to a broader hacker ecosystem.
5CA denies its systems were compromised
5CA publicly rejected claims that its infrastructure was hacked or that it managed the affected government-issued IDs, saying the incident occurred outside its systems. The company said its access controls, encryption, and monitoring remained secure and attributed the incident to human error without further detail.
5CA is publicly identified as the vendor tied to the incident
Initial reporting clarified that the third-party involved was 5CA rather than Zendesk, narrowing attribution of the breach to Discord's outsourced support environment. Discord had not confirmed that 5CA itself stored the exposed government ID photos.
Discord revokes vendor access and begins incident response
Following confirmation of the breach, Discord revoked the affected vendor's access, isolated impacted systems, launched an investigation, and began notifying affected users. These actions were part of its immediate response to the third-party compromise.
Discord confirms third-party breach affecting about 70,000 users
In October 2025, Discord confirmed a data breach tied to a third-party customer support vendor and said roughly 70,000 users had government ID photos exposed. The company also clarified that the incident was not as large as the attackers had claimed.
Hackers claim theft of Discord user data including IDs
Threat actors claimed they had stolen data from 5.5 million Discord users, including government IDs and partial payment details. Later reporting indicated the actual confirmed impact was far smaller than the attackers' claim.
Support agent account at BPO vendor is compromised
Discord said the breach was enabled by a compromised customer support agent account at a business process outsourcing vendor, allowing unauthorized access to user data held in support systems. The exact date was not disclosed, but it preceded Discord's October 2025 breach confirmation.
Related entities
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Sources
4 references tracked. Mallory keeps watching after this page renders.
Discord Breach: What We Know So Far?
socradar.io
Open source70,000 government IDs leaked in Discord data breach
proton.me
Open sourceThird-party blamed for Discord hack refutes compromise
scworld.com
Open sourceThe company Discord blamed for its recent breach says it wasn't hacked
engadget.com
Open sourceSee the full picture, correlated to your attack surface.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.


