What data was exposed, and was it protected?
Email addresses and account passwords. Some passwords were stored hashed or encrypted, but reporting on the incident notes the extent of any plaintext exposure is unclear. KDDI's own statement is careful hedging: there "remains a possibility that customers' email addresses and passwords were obtained by unauthorized third parties."
Answered in
One Vendor Flaw Just Exposed 14.2 Million Logins Across Six Japanese ISPsA flaw in one unnamed vendor's software let attackers into a shared email platform, exposing up to 14.2 million accounts across six Japanese ISPs.
Read the full analysisOther questions this article answers
More development best practices questions
- What did OpenAI’s Habitat team change?
- Does the reported 12× read improvement mean another team should copy the design?
- Does the Python Typing Survey measure all Python developers?
- Do Python type hints enforce types at runtime?
- What is interactive refactoring in gopls?
- Is interactive refactoring already part of the official LSP standard?
- What does Meta mean by human-on-the-loop software engineering?
- Does Meta's Forum project prove that AI can replace a software team?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Development Best Practices beat.