Osaka gap: 1 MILLION emails of government expostos, Japan under attack
On November 16, 2026, the government of Osaka (second largest city of Japan) discovered that he was hacked.
More than 1 million addresses, email were exposed.
It was not a bank.
It was not a private company.
It was the government of a city of 2.7 million people.
What happened
The gap
FACT (according to Just Security):
Osaka City Government suffered a data gap.
More than 1 million addresses, email exposed.
Attack Vector: distribution Service e-mail of committed third party.
Scale
1 million emails means:
- Potentially emails of citizens
- Potentially emails of employees of the government
- Potentially emails of public officials
- Probably including access to government services
The third committed
FACT: The attack was via the distribution service of email of the third party.
This third party is probably used by multiple cities and governments.
Gap in one = impact on many.
Why it was possible to
Vulnerability: a Third party again
As The Post. As Uber. As many others:
The attacker committed to Osaka directly.
Committed to the third party that Osaka trust.
The pattern emerges
In November 2026:
- The Post: committed Third party (22M people)
- Uber: committed Third party (150K people)
- Osaka: committed Third party (1M+ emails)
- TSMC: cloud Provider committed (46K people)
- Claude Code: Fireworks IA compromised (Anthropic affected)
The pattern is clear: The majority of breaches are via third parties.
The impact
For citizens of Osaka
- Emails potentially exposed
- Privacy of communications compromised
- Access to government services potentially affected
For the government of Osaka
- Breach of trust in public institutions
- Possible research of regulators
- Potential impact on government services
Japan
- Multiple cities may be affected (if third party is shared)
- Government infrastructure is vulnerable
- Question on security of public services
How it happened (analysis)
Phase 1: Engage service email
The distribution provider email was compromised via:
- Credentials weak
- Vulnerability is not patched
- Phishing employee
Phase 2: Access to Osaka
With credentials of a third party:
- Attacker agreed to systems of Osaka
- Access was enabled automatically (trusted third party)
Phase 3: Exfiltration of emails
Extracted 1 million+ addresses email.
How to 24Cevent would have helped
If Osaka had 24Cevent correlating third parties:
Detection of the third party committed
When you access pattern changed:
- Monitoring: ‘Pattern of access of the third is abnormal’
- Correlation: ‘access Volume is different from the normal’
- Action: immediate Investigation
Anomaly detected before exfiltration mass.
Exfiltration blocked
If exfiltration had already begun:
- Monitoring: ‘1M+ emails to be downloaded’
- Correlation: ‘Volume anomalous from the third’
- Action: Lock-immediate download
Exfiltration is stopped in seconds.
Correlation with other gaps
If 24Cevent had global intelligence:
- ‘This pattern of attack is identical to that of The Post 3 days ago’
- ‘Third was probably committed by the same assailant,’
- ‘Warning to governments that use the same third-party’
String of commitments stops.
The lesson for governments
Governments are targets priority for attackers because:
- Access to national data critical
- Major infrastructure
- High impact value
But governments often use third shared:
- Email providers
- Cloud providers
- Shared services providers
A third party committed = Multiple governments committed.
SOURCES CHECKED: