Home › Intelligence › Brief
BREACH BRIEF🟠 High Breach

NetEase (163.com) Breach Exposes 235 M Email Addresses and Plain‑Text Passwords

In October 2015, NetEase’s 163.com email service leaked roughly 235 million user records, including email addresses and passwords stored in clear text. The breach underscores the importance of robust password‑hashing controls and continuous credential‑leak monitoring for audit readiness.

LiveThreat™ Intelligence · 📅 October 07, 2026· 📰 haveibeenpwned.com
🟠
Severity
High
BR
Type
Breach
🎯
Confidence
Medium
🏢
Affected
3 sector(s)
✅
Actions
4 recommended
📰
Source
haveibeenpwned.com

NetEase (163.com) Breach Exposes 235 M Email Addresses and Plain‑Text Passwords

What Happened — In October 2015, the Chinese internet portal NetEase (operating the 163.com email service) suffered a data breach that released approximately 234.8 million user records. The exposed data includes email addresses and passwords stored in clear text. Although the breach is flagged as “unverified,” multiple Have I Been Pwned (HIBP) users have confirmed that their passwords appear in the dump, indicating the data’s authenticity.

Why It Matters for Trust & Control Assurance

  • Demonstrates the risk of weak credential storage practices—plain‑text passwords bypass the fundamental control of protecting authentication secrets.
  • Highlights the need for continuous monitoring of credential exposure and rapid evidence collection to support audit readiness.
  • Aligns with the control objective of Identity & Access Management (ensuring passwords are hashed, salted, and protected) that maps to many frameworks (e.g., NIST CSF 2.0, ISO 27001).

Who Is Affected – Large‑scale email service providers, SaaS platforms handling user credentials, and any organization whose users may have reused these compromised passwords.

Recommended Actions

  • Verify that all stored passwords are hashed with a strong, adaptive algorithm (e.g., Argon2, bcrypt).
  • Implement credential‑leak detection services to receive alerts when user passwords appear in public dumps.
  • Conduct a forced password reset for affected accounts and communicate securely with users about the breach.
  • Document the incident in your control‑assurance logs to provide defensible evidence for auditors.

Technical Notes – The breach surface includes email addresses and clear‑text passwords; no specific vulnerability or CVE is disclosed. The attack vector remains unknown, but the outcome points to inadequate password storage controls.

📰 Original Source
https://haveibeenpwned.com/api/v3/breach/NetEase ↗

This LiveThreat Intelligence Brief is an independent analysis. Read the original reporting at the link above.

From the Verisq platform · Trust Operations

Could you prove your access controls held up here?

Credential and access failures map directly to identity and access-control requirements in every major framework. The Verisq AI Trust Operations platform shows where your evidence is thin before an auditor — or an attacker — finds out.

Explore the Verisq AI Trust Operations platform →