Topic · 25 articles
Cybersecurity and data breaches in Japan
Most breach notices in Japan describe an incident that started somewhere else: at a vendor, a hosting company, a website builder or a contractor with an admin login. The organization that writes to its customers is often the last to learn what happened.
These articles follow that reporting. They cover the 2026 breach wave and the vendors behind it, ransomware and the shutdowns it causes, email authentication, card numbers kept longer than they should be, and how companies and the government respond once a notice is out. Each one cites the public notices it draws on, and the counts come from the Japan Cybersecurity Tracker.
If you run a small or mid-sized business, start with what an outsider can already see: your domain, your email authentication, the logins your vendors hold and the data you keep longer than you need.
All articles in this topic
25- Japan's smartphone location data is for sale. Nikkei just proved it. Nikkei Asia obtained brokered smartphone location data covering more than 40 million devices in Japan and traced phones through the prime minister's office and over 300 Self-Defense Force facilities. What the investigation found, why Japanese law only partly covers it, and what your business should do about it.
- Fugaku's Real Leak Was the Keys A public status dashboard let attackers into Fugaku, Japan's flagship supercomputer. The SSH keys left in users' home folders could open systems far beyond RIKEN.
- Optimizely supply-chain attack: what happened, who was hit, and what to check now Attackers abused Optimizely's signup flow to inject malicious JavaScript into customer projects. What happened and how to reduce third-party script risk.
- Not every outage is an attack. Your plan should work either way. ATMs went dark at 128 of Japan's 254 shinkin banks (50.4%). Phones screamed a magnitude 9.9 warning for a giant quake that never arrived. It looked like an attack. It wasn't. Then Microsoft 365 failed for half a day, and that wasn't an attack either.
- Muji data breach: the card numbers that should have been deleted Muji may have exposed 1.09 million full card numbers it should have deleted. What failed, where Stripe helps, and what businesses in Japan should change.
- Japan cyberattack tracker update: what 1,435 public notices show so far My Japan cyberattack tracker now holds 1,435 incidents disclosed from 1 June to 10 November 2026. As the record grows, the patterns are getting clearer.
- Japan Is Right to Act on Data Leaks. Blocking Won't Get It There. Japan's ministry will study blocking sites that publish leaked data. Blocking can't reach dark web leak sites or reposts. Fixing systems before data is stolen can.
- Six weeks, 553 incidents: Japan's breach wave runs through vendors The Japan Cybersecurity Tracker's first six weeks: 54% of disclosed incidents came through a vendor, and each vendor's customer list decided where the victims were.
- GMO's own hackers saw it coming. The fix wasn't fast enough. GMO's own ethical hackers flagged its FX cloud service before attackers used stored broker passwords to drain accounts. What the delay teaches.
- The front door held. They came in through the vendor's back office. Attackers placed trades in IwaiCosmo Securities customer accounts without stealing a single password. They went through a misconfigured admin function at Trade Works, the vendor that runs the trading system.
- Whom Now Shall We Trust? After the Arcadia breach, a real Japanese disaster-alert system sent 1.42 million phishing emails and police contact lists leaked. What that does to trust in authorities, and how to protect yourself.
- October 17 was the day Japan's technical debt came due SoftBank, Carsensor, 2nd STREET and GEO all went dark on one day. Shutting everything down is what technical debt leaves you with when attackers arrive.
- Commune data breach: one community platform, 29 organizations exposed A flaw in Commune, the community SaaS behind fan sites for Suzuki, Mazda, Panasonic and LINE Yahoo, exposed about 307,000 members. What to ask your vendors.
- Studio.Design breach: your website builder held your keys The Studio breach exposed form data, API keys, and the key to decrypt them. What it means for Japanese companies on no-code website builders, and what to do.
- Doing something isn't the same as fixing it Yoshinoya blocked foreign IPs. Times Car users reissued licences. Fixes chosen without understanding the breach change nothing, but feel like they do.
- Nobody had to hack Japan's earthquake warning A false M9.9 warning was cancelled after eight minutes, and Japan asked if it had been hacked. The breach wave has made distrust the reflex. Why that matters.
- The PC left in a Kobe hotel room Two people hid a computer on a Kobe hotel's Wi-Fi and sent phishing mail through it. The gap was monitoring, and hotels, offices, and shared spaces can close it.
- Quoted in The Japan Times on Japan's phishing kit crackdown The National Police Agency took down 34 domains selling phishing kits. I told The Japan Times not to wait. Encrypted DNS, passkeys, and a harder rule for links.
- Sovereign AI, made elsewhere Japan says it wants AI sovereignty. When the breach wave hit, its digital minister called Anthropic. What that says about the system Japan runs on.
- You outsourced the work, not the responsibility Japan's 2026 breach wave keeps running through vendors. Why the companies that hired them still own the result, and what to check this week.
- Blood in the water: Japan's neglected basics are visible from a mile away Japan's 2026 breach wave lands in an environment of neglected basics anyone can see. Why that neglect does triple damage, and why the fixes are easy.
- Japan cyberattacks in 2026: what the breach wave reveals Lawson, Times Car, Skyticket, and IDCF Cloud exposed different failures in application access, data retention, supplier dependence, monitoring, and recovery.
- What functional cybersecurity control looks like in Japan Policies, vendors, and certificates are not control. How organizations of any size can prove they know their stack, limit authority, and recover from failure.
- Japan's data breaches: a cyberattack is not an explanation Japanese breach notices describe what attackers did and leave the institutional failure buried. Why victimhood does not end the question of custodianship.
- The 99.7% problem: Japan's SME cybersecurity exposure SMEs are 99.7 percent of Japanese businesses. What visible breaches at large companies imply for the much larger, less visible small-business attack surface.