Pay Tel Communications Exposes Sensitive Inmate Data in Major Security Breach

Pay Tel Communications Exposes Sensitive Inmate Data in Major Security Breach

First seen 28 May 2026, 18:56 UTC Techcrunchwww.upguard.comleakd.comScworld 78% similarity 66.0

Article Content

Browse articles
ThreatCluster

On May 4, 2026, UpGuard researchers found a publicly exposed Azure storage bucket belonging to Pay Tel Communications, revealing 3.4 million documents, including 300,000 driver’s licenses and sensitive inmate communications. This incident follows a ransomware attack by the DragonForce gang on June 15, 2025, which compromised 399 GB of data from 121 detention centers. The data breach affects inmates and their families, as well as correctional officers, with personal and legal documents exposed. Pay Tel has not publicly acknowledged the latest security incident or confirmed whether affected individuals will be notified. The exposure highlights ongoing issues with cybersecurity practices within the corrections industry.

Key Points: • 3.4 million documents, including 300,000 driver’s licenses, were exposed due to misconfigured storage. • The breach follows a ransomware attack in June 2025, indicating ongoing security vulnerabilities at Pay Tel. • Sensitive inmate communications and personal documents were accessible online, impacting inmates and their families.

ThreatCluster AI

Timeline

2025-06-15
Ransomware attack on Pay Tel Communications
DragonForce gang exfiltrated 399 GB of data affecting 121 detention centers, targeting inmate communications.
leakd.com
2026-05-04
Public exposure of Azure storage bucket
UpGuard discovered an unsecured Azure bucket belonging to Pay Tel, exposing 3.4 million documents.
www.upguard.com
2026-05-07
Pay Tel notified of data exposure
UpGuard alerted Pay Tel about the exposed data, which included sensitive personal information.
www.upguard.com
2026-05-28
TechCrunch reports on data exposure
TechCrunch highlights the security lapse at Pay Tel, detailing the sensitive data that was exposed.
Techcrunch

Community

Browse all →