Nikkei Confirms Hackers Stole 1.8 Million Records From Cloud Service
Japanese media giant Nikkei says attackers used compromised credentials to steal data from a development cloud service, exposing personal details of 150,000 users.

Key points
- Hackers accessed a cloud service used for system development on the morning of October 7.
- Approximately 150,000 records contained names, addresses, emails, phone numbers, and birth dates.
- Nikkei revoked credentials immediately and found no evidence of data misuse as of October 16.
Japanese media giant Nikkei disclosed a data breach, confirming that hackers stole more than 1.8 million records from a cloud service used for system development. The company stated that attackers used previously compromised credentials to gain access to the environment on the morning of October 7, according to SecurityWeek.
Nikkei reported that the total volume of stolen data reached 1.83 million records. The company clarified that about 1.68 million of these records contained only information that cannot be used to identify an individual. This distinction is crucial for understanding the scope of privacy exposure for the broader user base.
Context and Incident Details
The remaining compromised records included sensitive personal data for a smaller subset of users. Specifically, 150,000 records contained names, addresses, email addresses, phone numbers, and dates of birth. Another 120,000 records contained only email addresses. Nikkei emphasized that no credit card information was compromised in this attack.
Upon identifying the breach, Nikkei revoked the compromised credentials immediately. The company stated it will take additional security measures if necessary and has notified relevant regulators. The investigation into the scope of the incident and the nature of the compromised data is ongoing, according to the company's disclosure.
Impact and Previous Breaches
As of October 16, Nikkei found no evidence that the stolen personal information has been misused. The company also noted that the incident did not result in disruptions to services or any data tampering. Nikkei apologized for the inconvenience and stated it will inform individuals if the leakage of personal information is confirmed.
This announcement comes less than a year after Nikkei disclosed a previous data breach stemming from a Slack account hack. The recurring nature of these incidents highlights the ongoing challenges media giants face in securing third-party communication and development tools.
What should you do?
Security professionals should monitor for unauthorized access attempts on cloud development environments. Organizations must ensure that credentials for critical infrastructure are rotated regularly and that multi-factor authentication is enforced. Users should remain vigilant for phishing attempts that may leverage leaked contact information.
What to do and how to stay safe: Nikkei
- Review access logs for cloud development services to detect unusual login patterns or credential reuse.
- Enforce multi-factor authentication on all accounts with access to sensitive data or development environments.
- Monitor email inboxes for suspicious messages that may attempt to exploit known contact information.
- Verify that incident response plans include procedures for rapid credential revocation upon detection of compromise.
Step-by-step guide: Social Engineering Warning Signs and How to Respond
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
How many records contained personally identifiable information in the Nikkei breach?
Approximately 150,000 records contained names, addresses, email addresses, phone numbers, and dates of birth, while 120,000 contained only email addresses.
Did the attackers steal financial data from Nikkei?
No, Nikkei stated that no credit card information was compromised in the attack.
When did the hackers access the cloud service?
The hackers accessed the cloud service on the morning of October 7 using previously compromised credentials.


