Skip to navigation

Threat reportData BreachTL-2026-2952

Nikkei discloses Microsoft 365 and Google Workspace employee account compromises; ~9,000 phishing emails sent

mediumACTIVE

Japanese media group Nikkei disclosed two separate employee-account intrusions: a Microsoft 365 account used on September 30, 2026 to send about 9,000 emails linking to malicious websites, and a Google Workspace account accessed from late July (found early August after a Google notification) that may have exposed names and email addresses of 1,646 people.

Key facts

IdentifiersTL-2026-2952
SeverityMEDIUM
Affected productsNikkei Inc. Employee Microsoft 365 account (cloud email); Nikkei Inc. Employee Google Workspace account
MITRE ATT&CK techniquesT1078.004 Cloud Accounts, T1114.002 Remote Email Collection, T1534 Internal Spearphishing, T1566.002 Spearphishing Link, T1586.002 Email Accounts, T1656 Impersonation, T1684.001 Impersonation
MotivationUNKNOWN
Target sectorsnews - media, news publishing, journalism
Target regionsjapan
Detection rules9 (1 shown free)
Sources8 cited sources

Detection coverage

As of 2026-10-06, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-2952 across Splunk SPL, Microsoft KQL and Sigma, covering 10 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Suspicious Inbox Rule, Forwarding or Delegate/SendAs Grant on a Mailbox (Collection, Hiding, Impersonation Setup)

Detects creation or modification of inbox rules or mailbox forwarding that forward/redirect or hide mail (T1114.003, T1564.008), and Full Access / SendAs / SendOnBehalf grants that let a third party read or impersonate the mailbox (T1098.002). Compromised cloud mailboxes are commonly configured this way to collect mail (the Nikkei incident exposed recipient names, addresses and some email contents). Rule/forwarding setup is a hunting hypothesis consistent with the remediation guidance, not a confirmed Nikkei TTP.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1114.002, T1114.003, T1564.008, T1098.002
  • Data sources: o365:management:activity, OfficeActivity, exchange_audit
  • Severity: medium
  • Confidence: medium

Splunk SPL

index=o365 sourcetype="o365:management:activity" Workload=Exchange (Operation="New-InboxRule" OR Operation="Set-InboxRule" OR Operation="UpdateInboxRules" OR Operation="Set-Mailbox" OR Operation="Add-MailboxPermission" OR Operation="Add-RecipientPermission") earliest=-24h
| eval rule_params=mvjoin(mvzip('Parameters{}.Name','Parameters{}.Value',"="),";")
```forward/redirect (T1114.003), delete/hide (T1564.008), delegate/SendAs grants (T1098.002)```
| eval behaviour=case(match(rule_params,"(?i)(ForwardTo=|ForwardAsAttachmentTo=|RedirectTo=|ForwardingSmtpAddress=|ForwardingAddress=)"),"forwarding", match(rule_params,"(?i)(DeleteMessage=True|MarkAsRead=True|MoveToFolder=.*(RSS|Archive|Conversation History|Deleted Items))"),"hiding_rule", match(rule_params,"(?i)AccessRights=.*(FullAccess|SendAs|SendOnBehalf)"),"delegate_grant", true(),null())
| where isnotnull(behaviour)
| table _time UserId Operation behaviour ClientIP rule_params

Microsoft KQL

OfficeActivity
| where TimeGenerated > ago(24h)
| where OfficeWorkload == 'Exchange'
| where Operation in ('New-InboxRule', 'Set-InboxRule', 'UpdateInboxRules', 'Set-Mailbox', 'Add-MailboxPermission', 'Add-RecipientPermission')
| extend Behaviour = case(
    Parameters has_any ('ForwardTo', 'ForwardAsAttachmentTo', 'RedirectTo', 'ForwardingSmtpAddress', 'ForwardingAddress'), 'forwarding',
    Parameters has_any ('DeleteMessage', 'MarkAsRead', 'MoveToFolder'), 'hiding_rule',
    Parameters has_any ('FullAccess', 'SendAs', 'SendOnBehalf'), 'delegate_grant',
    '')
| where isnotempty(Behaviour)
| project TimeGenerated, UserId, Operation, Behaviour, ClientIP, Parameters

Sigma

title: Exchange Online Inbox Rule or Forwarding Set With Forward or Delete Action
id: 2e8b6d14-95c3-4a7f-b1d0-6f3c8a4e9b22
status: experimental
description: Detects inbox rules or mailbox forwarding that forward, redirect or delete mail in Exchange Online, a common post-compromise collection and concealment step for hijacked mailboxes.
references:
  - https://therecord.media/nikkei-cyberattack-japan-data
author: Threadlinqs Team
date: 2026-10-05
tags:
  - attack.collection
  - attack.t1114.002
  - attack.t1114.003
  - attack.defense-evasion
  - attack.t1564.008
  - attack.persistence
  - attack.t1098.002
logsource:
  product: m365
  service: exchange
detection:
  selection_op:
    Operation:
      - 'New-InboxRule'
      - 'Set-InboxRule'
      - 'UpdateInboxRules'
      - 'Set-Mailbox'
      - 'Add-MailboxPermission'
      - 'Add-RecipientPermission'
  selection_params:
    Parameters|contains:
      - 'ForwardTo'
      - 'ForwardAsAttachmentTo'
      - 'RedirectTo'
      - 'ForwardingSmtpAddress'
      - 'ForwardingAddress'
      - 'DeleteMessage'
      - 'MarkAsRead'
      - 'FullAccess'
      - 'SendAs'
      - 'SendOnBehalf'
  condition: selection_op and selection_params
falsepositives:
  - Users legitimately forwarding mail to a personal or delegate address
  - Admin-configured forwarding for departing staff
level: medium

Known false positives:

  • Legitimate user forwarding or out-of-office style rules
  • Admin-managed forwarding for departing employees
  • Helpdesk or executive-assistant delegate and SendAs grants

Tuning notes: Restrict to external forwarding targets (exclude your own domains) and exclude approved service accounts. Correlate with a preceding anomalous sign-in for the same UserId.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • Google Workspace Login From a New Country for an Established User · unlock with TL Creds
  • Bulk Mailbox Access From a New IP (Remote Email Collection) · unlock with TL Creds
  • Link-Bearing Mass Mail From a Trusted Mailbox to Prior Contacts · unlock with TL Creds
  • Successful Legacy-Protocol Sign-In to [indicator] (MFA Bypass Path) · unlock with TL Creds
  • Google Workspace Native Suspicious Login Alert Events · unlock with TL Creds
  • Recipient-Side Malicious URL Click or Post-Delivery Removal Alert From Trusted Sender · unlock with TL Creds
  • Cloud Account Takeover - First Successful Entra ID Sign-In From a New Country · unlock with TL Creds
  • Bulk Outbound Mail Burst From a Single Mailbox (Trusted-Sender Mass Phishing) · unlock with TL Creds

Indicators of compromise

As of 2026-10-06, Threadlinqs Intelligence tracks 10 indicators of compromise for TL-2026-2952.

10 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

No actor is attributed and any link between the incidents is undetermined.

On October 4, 2026 Nikkei Inc. publicly disclosed two separate unauthorized-access incidents involving employee cloud accounts, as reported by The Record (published 2026-10-05) and corroborated by The Cyber Express, Alo Japan and Rankiteo.

Incident 1 - Microsoft 365: an unauthorized third party gained access to an employee's Microsoft 365 account. On September 30, 2026 the account was used to send approximately 9,000 emails containing links to malicious websites. Recipients included Nikkei staff and external parties, among them journalistic sources and contacts who had previously corresponded with employees. Exposed data comprises recipients' names, email addresses and, in some cases, email contents. Nikkei changed the account password, contacted recipients asking them to delete the messages and treat them with caution, and reported that no further unauthorized access has been detected.

Incident 2 - Google Workspace: a separate employee's Google Workspace account was accessed by an unauthorized party from late July 2026. Nikkei discovered the access in early August after a notification from Google. Names and email addresses of 1,646 people (employees and business partners) may have been exposed. Nikkei states that no reader or journalistic-source information was involved. Passwords were reset and no subsequent unauthorized access has been identified. The matter was reported to Japan's Personal Information Protection Commission; Nikkei found no evidence of misuse.

The initial access vector for both incidents (credential phishing, infostealer, MFA bypass or other) has not been disclosed, nor whether the two incidents are related. No technical indicators (sender addresses, URLs, domains, IPs, hashes) have been published, and no threat actor has been named. Context: Nikkei was previously hit by a ransomware attack on its Singapore unit (Nikkei Group Asia Pte. Ltd., May 2022) and by a Slack workspace compromise via an employee's malware-infected PC (disclosed late 2025, reportedly 17,000+ people exposed). The recurrence of account-centric intrusions against the same organization is relevant to defenders. Because the phishing mail originated from a legitimate, trusted Nikkei mailbox and targeted journalistic sources, recipients may have been especially likely to trust the links.

MITRE ATT&CK techniques by tactic:

Initial Access

T1078.004 Cloud Accounts; T1566.002 Spearphishing Link

Collection

T1114.002 Remote Email Collection

Lateral Movement

T1534 Internal Spearphishing

Resource Development

T1586.002 Email Accounts

Defense Evasion

T1656 Impersonation; T1684.001 Impersonation

Remediation

Immediate actions

  • Reset passwords and revoke active sessions/tokens for any affected Microsoft 365 and Google Workspace accounts
  • Review Entra ID sign-in logs and Google Workspace login audit logs for unfamiliar IPs, locations and user agents
  • Search mail flow logs for bulk outbound messages from affected mailboxes and purge delivered phishing messages
  • Notify external contacts who received the messages and ask them not to open links

Workarounds

  • Apply outbound mail rate limits per user
  • Restrict legacy authentication and unmanaged-device access to cloud mail

Longer-term hardening

  • Enforce phishing-resistant MFA (FIDO2/passkeys) for all cloud identities
  • Alert on anomalous outbound mail volume and new inbox rules or forwarding
  • Enable Google security-alert and Microsoft identity-protection risk-based conditional access
  • Train staff and external-facing journalists on trusted-sender phishing

Affected and fixed versions

  • Nikkei Inc. — Employee Microsoft 365 account (cloud email)
    Vulnerable versions: one employee account compromised
    Fixed in: password changed
  • Nikkei Inc. — Employee Google Workspace account
    Vulnerable versions: one employee account; 1,646 people potentially exposed
    Fixed in: password reset

Timeline

Last updated · 2 updates · revalidated 2× · latest source

  • Prior incident: ransomware attack on Nikkei Group Asia Pte. Ltd. (Singapore headquarters), disclosed 2022-05-19.
  • Prior incident (month approximated): Nikkei Slack workspace breached via an infostealer on an employee's personal computer; 17,368 people's data exposed.
  • Early March 2026 (exact day not disclosed): separate unauthorized external login to a Microsoft 365 account at U.S. subsidiary Nikkei America (up to 291 individuals; disclosed 2026-05-07). Sources do not link it to the later incidents.
  • Approximate date (disclosed only as 'late July'): unauthorized access to an employee's Google Workspace account begins.
  • Approximate date (disclosed only as 'early August'): Nikkei discovers the Google Workspace access after a notification from Google; passwords reset.
  • Approximate date (disclosed only as 'September 2026'): a Nikkei employee's Microsoft 365 account is accessed without authorization.
  • Nikkei BP (group company) discovers an employee account accessed without authorization after the employee entered credentials on a phishing email impersonating a Nikkei newspaper company account; 26 names and email addresses potentially exposed. Not explicitly stated to be the same event as the Microsoft 365 incident.
  • Nikkei changes the compromised Microsoft 365 account password the same day as the ~9,000-email phishing run; recipients are later contacted individually.
  • Compromised Microsoft 365 account used to send about 9,000 emails with links to malicious websites to staff, journalistic sources and past contacts.
  • Nikkei Inc. publicly discloses both incidents, reports to Japan's Personal Information Protection Commission and asks recipients to delete the messages.
  • Nikkei publishes its primary announcement (No. 1555) covering both incidents; BleepingComputer covers it on 2026-10-06.
  • The Record and other outlets report the intrusions; no attribution, no technical indicators, and no link between the two incidents established.

Update history

Sources cited

Previous and next in data breach

Drafted by the Threadlinqs research pipeline from 8 sources; published ; last updated .

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats