ENGLISH Contact
BUSINESS── ARTICLE 020── ── 12 MIN READ

280 data leaks in 47 days: counting every one in Japan reveals apps' back doors under attack, and the arrival of AI that can hack

DATA WORLD collected every leak and intrusion disclosed in Japan from September 1 to October 17, 2026: 280 in all. The main techniques were taking apart smartphone apps to abuse weakly protected APIs, and breaking into contractors and cloud platforms where data gathers. Just before the wave, an open-weight model with strong hacking skills became downloadable by anyone, as experts had long warned. Do defenders need AI too, and how do South Korea and the EU punish breaches?

In a dark data-center corridor, DATA WORLD editor-in-chief Kaito Ogasawara looks at the camera with a grave expression as blank membership cards and envelopes stream out of an open server cabinet behind him. Text: "THE LEAK MACHINE" and "280 LEAKS IN 47 DAYS"
This autumn in Japan, hardly a day went by without a data leak in the news.

Yamato Transport's pay-later service, the Nikkei newspaper group, SourceNext, the Yakiniku King and Burger King restaurant apps, Bookoff. Each story reports one company at a time. So how much is happening in total?

We at DATA WORLD decided to count. We collected every leak and intrusion disclosed in Japan in the 47 days from September 1 to October 17, 2026. The result: 280, about six a day.

Counting showed more than volume. Attackers were going through smartphone apps' "back doors" and the places where many companies' data gather. And shortly before the wave, at the end of August, an AI model with strong hacking skills was released in a form anyone can download and run. What experts had warned about for years seems to be arriving.

SHORT ANSWERS

Four questions about Japan's leak wave, answered up front

AI will keep making attacks cheaper. The surest defense is to harden with AI, and to shrink the data you have to protect.

Q1How much is happening?

280 disclosures in 47 days (DATA WORLD tally), across local governments, retail, schools, IT, travel and finance.
→ PART 01

Q2How is the data being stolen?

Mostly by taking apart smartphone apps to find their APIs (the back doors linking apps to servers) and abusing weak checks at scale. Hubs such as contractors and cloud platforms were also hit; about 40% of disclosures came that way.
→ PART 02

Q3Is AI doing the attacking?

No individual case has been confirmed as AI-driven. But at the end of August, an AI model with strong hacking skills was released for anyone to run, and versions with safety rails removed are circulating, just as lawmaker Takahiro Anno warned in April.
→ PART 03

Q4How should we defend?

Defenders need AI too: organizations using security AI widely see breaches cost $1.93 million less on average. But AI finds flaws faster than people fix them, and the surest defense is not holding data you don't need.
→ PART 04
01

280 in 47 days: we counted them all

We collected every disclosure, from September 1 to October 17, 2026, of a personal-data leak, unauthorized access or ransomware attack by a Japanese company, hospital, school, local government or national agency. The total was 280. Week after week, 25 to 50 disclosures kept coming.

Weekly counts of leak and intrusion disclosures in Japan from September 1 to October 17, 2026: 280 in total, 25 to 50 per week; 220 distinct incidents
Disclosures per week (first week September 1-6, last week October 12-17), including several organizations disclosing the same incident (DATA WORLD tally). (Compiled from organizations' notices (see also Macnica))

Merging disclosures from the same incident leaves 220. Of these, 24 exceeded a million records and seven exceeded ten million, all seven disclosed from mid-September on.

Largest incidentsScale (organization's own units)Technique (as disclosed)
Gyazo (screenshot sharing, Sep 16)User data, about 23.62 million recordsVulnerability in an image upload server
Shopserve (e-commerce platform, final report Oct 16)About 23.36 million peopleExploited vulnerability
SourceNext (software retail, Oct 15)Member data, 22,519,960 recordsMisuse of an API returning member data
EPARK Relax & Esthe (booking, second report Sep 24)About 22.18 million recordsNot disclosed
skyticket (travel booking, Oct 9)About 14.64 million records and moreThree separate routes
Burger King Japan (Oct 15)About 11.18 million recordsNot disclosed
Yakiniku King app (Oct 5)Member data, about 10.79 million recordsNot disclosed

Sources: organizations' notices and specialist media; compiled by DATA WORLD.

By sector, local governments and public bodies had the most incidents (43), followed by retail (26), schools (23) and IT and cloud (22). This is not one industry's problem.

The totals don't add up. Linkage is the real risk

Add up the 187 disclosures that gave a count and you get about 210 million, but that is not the size of the damage. Records, people and accounts are mixed, many are only "possible" leaks, and the same people appear in many leaks. Fancl and Attenir, for example, reported 834,947 records that covered 785,496 people.

What should worry us is separate leaks being joined. In data work, merging the same person across tables by email or phone number is called record linkage, and it works on leaked data too.

Fictional example of record linkage: a pay-later leak (name, address, phone, purchases), a car service booking leak (phone, birth date, car) and a members site leak (email, phone, birth date) join via phone numbers and email addresses into one person's address, age, contacts, recent purchases and the fact that they drive
A fictional example. Each leak is a fragment; joined by phone or email, they describe a person's life (DATA WORLD chart). (Personal Information Protection Commission (October 7, 2026))

On October 15, the shoe maker Moonstar disclosed that a fake email impersonating it contained past order details only the customer and company could know. A message quoting your real order history is easy to mistake for the real thing.

02

The targets: apps' back doors and data hubs

How is the data being taken?

The first thing that stands out is how many cases don't say. In our tally, fewer than half of the cyberattack incidents named a specific entry point. Macnica found that of 81 web-system leaks disclosed since July, only 16 explained the cause in enough detail. Ransomware (malware that encrypts data and demands a ransom) accounted for only 13 incidents in our tally.

The best clue is an alert issued on October 8 by JPCERT/CC, Japan's computer emergency response team. It listed broad scanning for known vulnerabilities, a flaw in an analytics tool, planted web shells, and, most characteristic of this wave, taking apart smartphone apps to abuse their APIs.

One number away from someone else's data

Behind the screen, an app talks to the server through windows called APIs. Take the app apart and you learn which window to ask, how, and what comes back. If the server doesn't check whether the person asking may see that data, it hands over other people's data too.

How weak API permission checks are exploited: 1, unpack the public smartphone app; 2, find the API endpoints and keys; 3, swap member IDs one by one; result: other people's data comes back if checks are weak
How an app's back door (API) gets abused. With sequential IDs, weak permission checks and no rate limits, changing a number returns someone else's data (DATA WORLD chart). (PPC WARNING (revised October 7, 2026), JPCERT/CC)

Japan's privacy regulator describes exactly this kind of API abuse case in material revised on October 7: changing the member number in a URL after logging in returned others' data. The causes were APIs left out of management, responses returning unneeded data, sequential member numbers and no limit on bursts of requests. SourceNext also said an API returning member information was misused.

Break one hub, reach many

The other target is hubs. In our tally, 112 of the 280 disclosures, about 40%, came via vendors or cloud services.

About 40% of disclosures (112 of 280) came via vendors or cloud services. Organizations disclosing from a single incident: 17 for ApplyNow, 14 for IDCF Cloud, 11 for Studio
One vendor or cloud incident led many organizations to disclose (DATA WORLD tally). (Compiled from organizations' notices (see also Nikkei xTECH))

A breach at the hiring platform ApplyNow led 17 organizations to disclose. A ransomware attack on IDC Frontier's cloud affected 495 companies and local governments. Yamato's pay-later service held buyers from about 4,100 online shops, and about 5.26 million records leaked, going back to orders from October 2018, eight years ago.

Try back door after back door until one has a weak lock, and go after the places where data gathers: that was this wave.

03

The warnings came true: hacking AI now runs on your own machine

Probing that many apps and windows by hand is hard work. Which brings us to AI.

First, what is confirmed: none of the 280 cases has been confirmed as AI-assisted. Here is why we nonetheless think AI's influence is large.

Hacking-capable AI that anyone can download

In April 2026, Anthropic gave a handful of companies limited access to Claude Mythos Preview, a model so good at finding and exploiting unknown software flaws that it was not released publicly.

Days later, AI engineer and House of Councillors member Takahiro Anno sounded the alarm in the Diet. On April 15 he said other companies could build similar models "within a few months at the earliest, a year at the latest", calling it a race against time.

It took about four and a half months. China's Z.ai released GLM-5.3 on August 14 and, about two weeks later, published its weights for anyone to download. On September 17, CAISI, the AI evaluation center at the US National Institute of Standards and Technology, called GLM-5.3 "the most cyber-capable open-weight model released to date".

Timeline from warning to reality: January 2024, the UK NCSC predicts AI will raise cyberattacks within two years; April 7, 2026, Anthropic gives limited access to a highly capable model; April 15, lawmaker Takahiro Anno warns others could follow within months, a year at most; late August, GLM-5.3 weights are opened to anyone; from mid-September, leaks of over 10 million records are disclosed in Japan
From warning to reality. No direct link between GLM-5.3 and Japan's leaks has been confirmed (DATA WORLD chart). (NIST CAISI (September 17, 2026), Diet records and others)

In October, Anno wrote on X that GLM-5.3 seemed "almost Mythos-class" and that his warning "has come true", urging faster action.

Views on the gap differ. In Anthropic's tests exploiting Chrome flaws, GLM-5.3 completed working exploits in 50 of 410 attempts against Mythos Preview's 56, nearly level. CAISI, looking across its full test suite, puts it about four months behind the best US models. Either way, hacking ability that was cutting-edge half a year ago is now available to anyone.

Safety rails, removed for about $4,400

Worse, a model you can run yourself is a model whose safety rails you can strip out.

Normal AI services are built to refuse to help with attacks. But with open weights, the refusal mechanism can be removed. When Anthropic tried, GLM-5.3's rate of refusing harmful requests fell from over 90% to a few percent, with little loss of capability. It cost about $4,400 in compute; an experienced team could do it for about $1,200.

Cost and effect of stripping an AI model's safety rails: about $4,400; the share of harmful requests refused falls from over 90% to a few percent
Open-weight models can have their refusals removed. Figures from Anthropic's tests (DATA WORLD chart). (Anthropic (September 29, 2026))

Versions advertised as having their safety rails removed are already posted on model-sharing sites. With the smaller GLM-5.3-Flash, Anthropic built an exploit chain for known Chrome flaws with about 20 minutes of human effort and about $20 in usage. Its conclusion: "a critical threshold in freely accessible capabilities has now been crossed".

What the veterans said years ago

None of this came out of nowhere. Security expert Bruce Schneier wrote in 2021 that "at computer speeds, hacking becomes a problem that we as a society can no longer manage". In January 2024, the UK's NCSC predicted AI would "almost certainly increase the volume and heighten the impact of cyber attacks over the next two years".

Japan's numbers point the same way. Suspicious probing for weaknesses rose to 13,687 per IP address per day in the first half of 2026, up 50.7%, according to the National Police Agency. Cyber Security Cloud saw more than 1,200 requests from 326 IP addresses in about 40 minutes, changing tactics in response to what came back, and suggested AI agents. Japan's NICT warned on October 13 that AI makes app analysis and flaw-finding more efficient, so attacks that analyze apps to hit servers may spread. Abroad, an attacker using AI agents finished an intrusion in under ten hours that would take humans about two weeks.

04

Defenders need AI too, but first hold less data

If attackers use AI, what should defenders do? Use it too.

On May 18, Japan's National Cybersecurity Office and nine ministries jointly warned about misuse of high-performance AI and urged organizations to act quickly, including by actively using high-performance AI for cyber defense: detecting threats, responding to incidents, finding flaws. Anno's October 12 proposals to the government put "AI against AI" first.

There is evidence it works. IBM's 2026 study found organizations using security AI and automation extensively had breaches costing $1.93 million less than those that don't.

Effect and limits of defensive AI: organizations using security AI extensively see breaches cost $1.93 million less; of 6,157 open-source flaws found by AI and reported to maintainers, 516 are fixed so far
AI helps defenders a lot, but fixing what it finds still takes people (IBM Cost of a Data Breach 2026 and Anthropic disclosures; DATA WORLD chart). (IBM (July 29, 2026), Anthropic (updated October 2, 2026))

But AI is no cure-all. Anthropic reported 6,157 AI-found flaws to open-source maintainers, yet knows of only 516 fixed. AI finds flaws fast; fixing them still takes people, and they can't keep up.

That is why, alongside hardening with AI, shrinking the data you hold matters just as much. However well you defend, breaches happen, and data you don't hold can't leak. Yamato's leak reached orders from eight years ago. Japan's privacy regulator noted on October 7 that failures to delete unneeded data had made some leaks more serious.

The basic locks matter too. JPCERT/CC's measures were rate limits on APIs, permission checks on every endpoint, least privilege, and deleting data past its retention period: plain defenses that matter more, not less, in the age of AI.

05

Others punish leaks; Japan moves to hold less

Abroad, one big difference stands out: how heavily a leak itself is punished.

Comparison of fines for leaks caused by weak security: South Korea up to 10% of revenue, with Coupang fined ₩624.7 billion; the EU up to 2% of revenue, with France's Free fined €42 million; Japan's new surcharges do not cover such leaks
Fines for leaks caused by inadequate security (DATA WORLD chart). (Korea JoongAng Daily, CNIL, PPC and others)

South Korea fines companies up to 3% of revenue when weak security leads to a leak; e-commerce giant Coupang was hit in June 2026 with a record ₩624.7 billion, with failure to delete departed members' data among the violations. A September amendment raised the cap to 10% of revenue for serious cases. In the EU, France's regulator fined the telecom operator Free and its mobile arm a combined €42 million for weak security and keeping departed customers' data too long.

Japan's privacy law amendment, passed in July, introduced surcharges for the first time, but they cover things like improper acquisition and sharing without consent, not leaks caused by weak security.

Still, Japan is moving.

Timeline: October 1, 2026, critical infrastructure operators must report cyber incidents; October 7-9, government bodies urge deleting unneeded data and giving contractors the minimum; January-March 2027, a star-rating scheme for contractors' security is due to open; April 2027, identity checks move to reading the IC chip; the amended privacy law takes effect by July 2028
Main changes from October 2026 through 2027 (DATA WORLD chart). (National Cybersecurity Office (October 9, 2026) and others)

One calm note for readers: an email or text that correctly quotes your order is not proof that it is genuine. If something looks off, check through the official app or a bookmark you already use, not a link in the message.

EDITOR'S TAKE ── Editor-in-Chief Ogasawara's reading

When attacks get cheap, design how much you hold

Checking 280 cases one by one, what stood out was not one careless company, but a world where the cost of attacking has suddenly dropped while services are still built the old way.

VIEW01

The warnings are no longer predictions

That AI would change hacking has been said for years. In 2026, hacking-capable AI became available to anyone, safety rails removable. The "months to a year" Anno warned of in the Diet took about four and a half months.

The link between this wave and AI is unproven. But defenders should assume that the effort needed to attack will keep falling.

VIEW02

Treat API locks like the front-door lock

Most of this wave exploited a design gap rather than advanced skill: not checking whether this person may see this record. An app's back doors can be read by taking the app apart. API permission design deserves the same weight as the lock on the front door.

VIEW03

The strongest defense is not holding the data

Defending with AI is now essential. But breaches still happen, and data you don't hold can't leak.

In Korea and the EU, holding too much data is itself a ground for punishment, and Japan's agencies are now all saying "delete what you don't use". Data is an asset, but also inventory that must be protected for as long as you hold it. The cheaper attacks get, the more the amount you hold decides how strong your defense is. Now is the earliest time to take stock.

SOURCES ── References

  1. DATA WORLD, Tally of leaks and intrusions disclosed in Japan, September 1-October 17, 2026 (compiled from organizations' notices, Security NEXT, ScanNetSecurity, piyolog, westeria and others)
  2. JPCERT/CC, Alert on recent unauthorized access to Japanese organizations (JPCERT-AT-2026-0030) (in Japanese) (October 8, 2026; updated October 9)
  3. Macnica, The run of leaks from web systems (in Japanese) (October 7, 2026)
  4. Personal Information Protection Commission, WARNING: preventing personal data leaks through unauthorized access (revised October 7, 2026) (in Japanese)
  5. Personal Information Protection Commission, Response to recent large-scale leaks (alert) (in Japanese) (October 7, 2026)
  6. Personal Information Protection Commission, Amendment of the Act on the Protection of Personal Information (Act No. 56 of 2026) (in Japanese) (July 17, 2026)
  7. Tokyo Shoko Research, Leaks of 1 million+ records in 2026 (in Japanese) (October 7, 2026)
  8. Cyber Security Cloud, Observations of recent unauthorized access in Japan (in Japanese) (October 9, 2026)
  9. Yamato Transport, Unauthorized access to the Kuroneko pay-later service, report 4 (in Japanese) (October 16, 2026)
  10. SourceNext, Leak of personal information (in Japanese) (October 15, 2026)
  11. Helpfeel, Unauthorized access to Gyazo (in Japanese) (September 16, 2026)
  12. Fancl, Leak of personal information through unauthorized access (in Japanese) (October 16, 2026)
  13. Moonstar, Possible leak of personal information, report 3 (in Japanese) (October 15, 2026)
  14. Nikkei xTECH, Ransomware attack on IDC Frontier affects 495 companies and local governments (in Japanese) (October 2026)
  15. National Police Agency, Cyber threats in the first half of 2026 (in Japanese) (September 2026)
  16. National Cybersecurity Office, Response to recent leaks through unauthorized access (in Japanese) (October 9, 2026)
  17. National Cybersecurity Office and nine ministries, Alert on cyberattacks using high-performance AI (in Japanese) (May 18, 2026)
  18. NICT, Warning on attacks that analyze Android apps to hit servers (in Japanese) (October 13, 2026)
  19. Diet record, House of Councillors Special Committee on Digital Society and AI (April 15, 2026; remarks by Takahiro Anno) (in Japanese)
  20. Diet record, House of Councillors Committee on Internal Affairs and Communications (April 21, 2026; remarks by Takahiro Anno) (in Japanese)
  21. ITmedia AI+, Anno: "my warning has come true" on GLM-5.3 (in Japanese) (October 6, 2026)
  22. Takahiro Anno, Seven proposals to the government (in Japanese) (note, October 12, 2026)
  23. NIST CAISI, CAISI's Assessment of Z.ai's GLM-5.3 Cyber Capabilities (September 17, 2026)
  24. Anthropic, GLM-5.3 and the spread of advanced cyber capabilities (September 29, 2026)
  25. Anthropic, Project Glasswing (April 7, 2026)
  26. UK NCSC, The near-term impact of AI on the cyber threat (January 24, 2024)
  27. Bruce Schneier, The Coming AI Hackers (April 2021)
  28. Palo Alto Networks Unit 42, An AI-Assisted Cyber Attack: Inside a Unit 42 Investigation (September 2, 2026)
  29. IBM, Cost of a Data Breach Report 2026 (July 29, 2026)
  30. Anthropic, Coordinated vulnerability disclosure (updated October 2, 2026)
  31. The Korea Herald, Coupang fined record 624.7 billion won over data leak (June 2026)
  32. Korea JoongAng Daily, Korea raises data breach fines to 10% of revenue (September 10, 2026)
  33. CNIL, €42 million sanction against FREE MOBILE and FREE (in French) (January 13, 2026)
  34. Cabinet Office and National Cybersecurity Office, Enforcement of the Active Cyber Defense laws (in Japanese) (September 2026)
  35. METI, Security rating scheme for supply chains (in Japanese)
  36. Financial Services Agency, Early review of identity verification after customer data leaks (in Japanese) (October 9, 2026)
#BUSINESS#Data breaches#Japan#API security#AI and security#GLM-5.3#Open-weight models#Supply chain#Privacy law#Cyberattacks