Key takeaways
- Nikkei (日本経済新聞社), publisher of Japan's leading business newspaper, disclosed two separate account breaches on October 4, 2026.
- On October 16, it disclosed a third, larger breach: credentials for a cloud service it uses for system development were stolen and used on October 7 to take about 1.83 million records. About 150,000 include names or contact details; the rest are identifiers.
- In one, attackers took over an employee's Microsoft 365 account and on September 30 sent about 9,000 phishing emails, including to news sources who had been in contact with Nikkei staff. Recipients' names and addresses, and the content of some emails, are believed to have leaked.
- In the other, an employee's Google Workspace account was accessed from late July. Nikkei found out in early August when Google notified it. Data on 1,646 people may have leaked.
- These are the third and fourth takeovers of a Nikkei cloud work account disclosed in under a year, after Slack (November 2025) and a Microsoft 365 account at its US subsidiary (May 2026).
- The phishing worked on at least one recipient. Nikkei BP, a Nikkei group publisher, says an employee gave away their login through a phishing email sent from a Nikkei employee's address, and that their mailbox was then accessed.
Update, October 6: Nikkei BP disclosed on October 4 that one of its employees had their email account taken over on September 30 after a phishing email from a Nikkei employee's address. See The phishing reached Nikkei BP.
Update, October 19: Nikkei BP says the 1.83 million records may include some data on customers of its own services. See A development cloud, 1.83 million records.
Update, October 17: Nikkei says about 1.83 million records were taken from a cloud service it uses for system development. See A development cloud, 1.83 million records.
What happened#
Microsoft 365: phishing sent to news sources#
According to Nikkei's notice:
- An employee's Microsoft 365 account was attacked. Nikkei believes a third party logged in without authorization.
- On September 30, about 9,000 impersonation emails were sent from the account, leading to malicious websites. They went to people inside Nikkei and to news sources and others who had exchanged emails with several Nikkei employees.
- The names and email addresses of recipients, and the content of some emails, are believed to have leaked.
- Nikkei changed the password and has seen no unauthorized logins since. It contacted recipients individually and asked them to delete the emails.
- It has reported the incident to the Personal Information Protection Commission and is still investigating the scope and the number of people affected.
Nikkei warns that more emails impersonating Nikkei and group company staff may follow.
The phishing reached Nikkei BP#
Nikkei BP, the Nikkei group's magazine and technology media publisher, disclosed a related incident on October 4. According to its notice:
- On September 30, an employee's email account was accessed without authorization.
- The employee's credentials were obtained through a phishing email that arrived from the email address of a Nikkei employee.
- Names and email addresses of 26 people the employee had corresponded with may have leaked.
- Nikkei BP cut off access to the account, reported to the Personal Information Protection Commission, and emailed the people affected.
Nikkei BP does not name the Nikkei account, but the date and description match the September 30 phishing sent from Nikkei's compromised Microsoft 365 account.
Google Workspace: found by Google#
In a separate notice the same day:
- An employee's Google Workspace account, used for work, was logged in to from outside without authorization from late July.
- Nikkei learned of it in early August through a notification from Google. It changed the password and has seen no unauthorized logins since.
- Email addresses, names and other data on 1,646 people, including employees and business partners, may have leaked. Nikkei says no reader or news source data is included, and no secondary harm has been found.
- It has reported the incident to the Personal Information Protection Commission.
A development cloud, 1.83 million records#
Added October 17, 2026.
On October 16, Nikkei disclosed a separate and larger breach:
| What was accessed | A cloud service Nikkei uses for system development. It does not name the service |
| How | The credentials used to access the service were "stolen by some means" |
| When | From the early hours to the morning of October 7, 2026 |
| Records taken | About 1.83 million, as of October 16 |
| With personal details | About 150,000 include a name, email address, postal address, phone number or date of birth. About 120,000 of those include an email address |
| Identifiers only | About 1.68 million are identifiers that cannot identify a person on their own |
| Not included | Credit card data |
| Response | Credentials revoked. Reported to the Personal Information Protection Commission on October 11. People affected will be notified individually |
Nikkei says it has seen no misuse of the data, no system outage and no tampering. It has not said whether this breach is connected to the account takeovers it disclosed earlier.
Update, October 19: On October 17, Nikkei BP, the group's magazine and technology media publisher, said the data leaked in Nikkei's breach may include some information on customers of Nikkei BP's services. It is still investigating and gave no numbers, services or data types. The two companies' services share the Nikkei ID login, which may be why, but neither has said so.
Five in under a year#
| Disclosed | Service | What happened | People | How it was found |
|---|---|---|---|---|
| Nov 2025 | Slack | An employee's personal PC was infected with malware, and the Slack credentials stolen from it were used to log in | 17,368, including chat history | Not stated |
| May 2026 | Microsoft 365 (Nikkei America) | Impersonation emails sent to business partners in early March | 291 | A business partner got in touch |
| Oct 2026 | Google Workspace | Unauthorized logins from late July | 1,646 | Notification from Google |
| Oct 2026 | Microsoft 365 | About 9,000 phishing emails sent on Sep 30, including to news sources | Under investigation | Not stated |
| Oct 2026 | Cloud service for system development | Stolen credentials used on Oct 7 | About 1.83 million records, 150,000 with personal details | Not stated |
The Slack breach is the only one where Nikkei has explained how the attackers got the credentials.
What we don't know yet#
Nikkei has not said:
- How the attackers obtained access to the Microsoft 365 and Google Workspace accounts
- Whether the accounts used multi-factor authentication
- How the September 30 phishing was detected
- How many other recipients entered their details on the phishing sites. At least one, at Nikkei BP, did
- Why the Google Workspace breach, found in early August, was disclosed two months later
- Whether the incidents are connected, including the October 7 development cloud breach
- How many of the 1.83 million records belong to Nikkei BP customers, and which services they used
- Which cloud service was used for development, how its credentials were stolen, and why production personal data was stored there
Our analysis#
The attackers used a real employee's mailbox#
The Microsoft 365 emails did not come from a look-alike address. They came from a real Nikkei account, to people who had actually corresponded with Nikkei staff. A source who receives an email from Nikkei staff they know has every reason to open it. That is what makes a compromised mailbox more dangerous than ordinary phishing, and why the victims of this incident are not only Nikkei but its contacts.
Nikkei BP shows how it spreads. A Nikkei BP employee received a phishing email from a real Nikkei address, entered their login, and lost control of their own mailbox the same day. Each mailbox taken over this way gives the attacker a new list of contacts who trust the sender. That is why Nikkei's warning that more impersonation emails may follow should be taken seriously by anyone who corresponds with Nikkei group staff.
For a news organization, the recipient list matters in itself. Nikkei says the names and addresses of recipients, including news sources, and some email content are believed to have leaked. Who a newspaper's staff correspond with is sensitive information. In its Slack notice, Nikkei pointed out that personal data held for reporting purposes is exempt from the breach reporting duty under Japan's privacy law, and that it reported voluntarily. It has again reported this case to the regulator.
Found by others#
In two of the five incidents, Nikkei learned of the breach from outside: a business partner in the US case, and Google in the Google Workspace case. In the Google Workspace case, unauthorized access had continued from late July until Google's notification in early August. Nikkei has not said how it detected the September 30 phishing.
"We changed the password"#
Each of the five notices describes changing the password or revoking credentials as the main response, and none mentions multi-factor authentication. From the notices alone, readers cannot tell whether it was in use. As a general point, though, when credentials are stolen by malware, as in the Slack case, the session tokens that keep a user logged in are often stolen too, so a password reset alone may not be enough to cut off access.
Four account takeovers across Slack, Microsoft 365 and Google Workspace in under a year suggest that the problem is not one product. The notices promise to "further strengthen security measures", but say nothing about what changed after each incident.
Personal data in a development environment#
Added October 17, 2026.
The October 16 disclosure raises a question Nikkei has not answered: why a cloud service used for system development held personal data on 150,000 people at all. Development and test environments are often less tightly controlled than production, with more people and tools holding credentials. In our view, real customer data should not be there; masked or synthetic data should be used instead. And as with the earlier takeovers, the way in was a stolen credential, not a software flaw.
Three platforms, three sets of accounts#
Nikkei employees used Slack, Microsoft 365 and Google Workspace for work. Each has its own accounts, login settings and logs, so each needs its own multi-factor authentication, monitoring and offboarding.
Public DNS records show that email for nikkei.co.jp, Nikkei's corporate domain, is handled by Microsoft 365. We found no sign in those records of Google Workspace being used for that domain, although that does not rule out its use under another domain. The notices do not say whether the Google Workspace account was part of a company-managed environment or a service an employee or team used on its own. If it was the latter, the company would have had less visibility, which may help explain why it took a notification from Google to find the breach.
What this means for readers#
- If you exchanged emails with Nikkei staff and received an unexpected message from them around September 30, 2026, especially one with a link, do not open the link. If you entered a password after clicking, change it immediately, and anywhere else you used it.
- Expect more impersonation. Nikkei warns that emails pretending to be from its staff or group companies may increase. Check through another channel before acting on unusual requests, and report suspicious emails through Nikkei's inquiry form.
- If your organization relies on cloud mail and chat, treat account takeover as a standing risk: require phishing-resistant multi-factor authentication, revoke sessions as well as resetting passwords after an incident, and watch for unusual outbound mail from user accounts.
Japanese terms at a glance#
| Japanese | Reading | Meaning |
|---|---|---|
| 日本経済新聞社 | Nihon Keizai Shimbunsha | Nikkei Inc. |
| 不正ログイン | fusei roguin | Unauthorized login |
| なりすましメール | narisumashi mēru | Impersonation email |
| 悪性サイト | akusei saito | Malicious website |
| 取材先 | shuzaisaki | News source, interviewee |
| 個人情報保護委員会 | Kojin Jōhō Hogo Iinkai | Personal Information Protection Commission |
We will update this article if Nikkei publishes the number of people affected by the Microsoft 365 breach or more on the cause.