Brosix and Chatox Data Breach: When 'End-to-End Encryption' Promises Fall Short

August 4, 2025

A massive data breach has exposed over 100 million unencrypted chat messages from two communication platforms that promised end-to-end encryption but failed to deliver on their security claims. The breach affects healthcare providers, government officials, and major corporations, raising serious questions about vendor security promises and third-party risk management.

The Breach Overview

Brosix Enterprise and Chatox are communication platforms owned by Stefan Chekanov that advertised themselves as secure, encrypted messaging solutions. However, a researcher discovered an unsecured backup containing 155.3 GB of data with over 100 million chat messages stored in plain text.

Key Findings:

The Encryption Promise vs. Reality

Both platforms made bold security claims:

Brosix advertised:

"All messages sent with Brosix are fully encrypted using end-to-end encryption technology, guaranteeing that your communication remains secure... Brosix uses AES (Advanced Encryption Standard, used by US government) with 256 bit keys."

Chatox claimed:

"Chatox employs encryption across all communications, making it an extremely secure communication and collaboration platform."

Yet the researcher found all chat messages, user credentials, and attached files stored in plain text on an unsecured backup server.

Healthcare Data Exposure

The breach exposed sensitive healthcare information, including:

This represents a significant HIPAA violation, as protected health information (PHI) was exposed without encryption or proper access controls.

Major Organizations Affected

Allstate Insurance

Government Officials

Other Affected Sectors

Third-Party Risk Management Lessons

This breach highlights critical lessons for organizations:

1. Verify Vendor Security Claims

2. Implement Vendor Due Diligence

3. Data Minimization

Compliance Implications

HIPAA Violations

Healthcare organizations using these platforms may face:

SOC 2 Considerations

Organizations with SOC 2 compliance should:

Immediate Action Steps

For Affected Organizations:

  1. Identify affected users and data
  2. Reset compromised credentials
  3. Notify affected individuals
  4. Assess regulatory reporting requirements
  5. Review vendor security practices

For All Organizations:

  1. Audit third-party communications tools
  2. Verify encryption claims
  3. Implement vendor security assessments
  4. Update incident response procedures
  5. Train staff on secure communication practices

The Broader Impact

This breach demonstrates the growing risk of third-party communications platforms and the importance of:

For organizations struggling with third-party risk management, see our guide on Third-Party Risk Management: Best Practices. For healthcare organizations concerned about HIPAA compliance, read our HIPAA Compliance Checklist. For companies evaluating their security posture, take our Compliance Posture Survey.

Need Help with Third-Party Risk Management?

Our team can help you:

  • Assess your vendor security practices
  • Develop third-party risk management programs
  • Create incident response plans
  • Ensure compliance with regulatory requirements
Schedule a Consultation
data breach, encryption, healthcare, third-party risk, compliance