mythsthe wider recordAsahi Group2025beverages and food / japan

everyone assumed:

the network box at one of our sites only puts that site at risk

what was actually true:

Asahi says an attacker came in through network equipment at one group site, used a password weakness to take administrator rights in its main data center, and stopped ordering and shipping across Japan in September 2025.

how it happened

  1. whoan attackerdevice and flaw not disclosed
  2. the gapa password weaknessused to take administrator rights in the main data center
  3. thenransomware runs at onceservers and some older company PCs encrypted
  4. the resultorders stop across Japanmanual orders until December
the gap that let it happen the result

what everyone assumed

Asahi has not said what it believed before the attack, so this belief is an inference from what its later notices describe. A large group runs many sites: breweries, offices, warehouses. Each site needs a connection back to the central systems, and that connection rests on a router, a firewall or a remote-access box in the building. Those devices look like plumbing. They are bought by the network team, configured once, and judged by whether the site stays online. If one of them were compromised, the natural assumption is that the trouble would stay near that site. The device sits at the edge, far from the data center and the accounts that run it.

what happened

Asahi published the route itself. Several pages in this record, Stryker and Collins Aerospace among them, have no known entry route. Asahi’s notices give the outline, though no device, vendor or flaw is named.

  • The disruption. On 29 September 2025 Asahi announced a system failure caused by a cyberattack, limited to Japan, which suspended order and shipment operations at its Japanese group companies and their call centres. On 3 October it confirmed that its servers had been hit by ransomware and that it had found traces of a possible unauthorised data transfer.
  • The way in. Its notice of 27 November 2025 says the attacker reached the data center network “through network equipment located at our Group’s site”. Ransomware then ran at the same moment across the network, encrypting data on several running servers and some PCs. The disruption began around 07:00 on 29 September, and Asahi cut the network and isolated the data center around 11:00, by its own account.
  • The ten days before. The recurrence-prevention notice of 18 February 2026, in English and Japanese, adds the middle of the story. About ten days before the disruption, the attacker entered through that network equipment, exploited a password vulnerability to take administrator rights in the main data center, and appears to have repeatedly entered and surveyed several servers, mainly outside business hours. Asahi says it cannot pin down the exact date of entry, and it does not describe what the password weakness was.
  • What was reached. The same notice says the encrypted machines included several servers and some company PCs that had not yet moved to the company’s newer zero-trust setup, and that some information stored on those older PCs was stolen. Recovery used backups confirmed to be safe, after the backup system had been suspended to keep the backup data intact.

Asahi does not say the entry device was a VPN. Its list of fixes in February 2026 does start there: it removed remote-access VPN equipment entirely to prevent re-entry through network equipment, rebuilt its communication routes and removed devices exposed to outside access. The account fixes come next: password changes and stronger authentication across all systems, and automated management of account lifecycles.

The ransomware group Qilin claimed the attack on 9 October 2025, according to Reuters, and Asahi has not confirmed who was behind it. At a press conference on 27 November 2025, chief executive Atsushi Katsuki said, as AFP reported, “We have not been in touch with the attacker”, and Reuters reported that no ransom was paid.

step by step

  1. sites connect to the group networkBy Asahi's later account, equipment at a group site connected to a network that reached the main data center.
  2. mid-September 2025in through one site, up to administratorAbout ten days before the disruption, Asahi says, the attacker came in through network equipment at a group site and used a password weakness to take administrator rights.the assumption breaks here
  3. 29 September 2025ransomware runs across the networkSystems failed around 07:00; Asahi cut the network and isolated the data center around 11:00, and ordering and shipping stopped.
  4. December 2025 to February 2026electronic orders return, the route is removedElectronic ordering resumed on 2 and 3 December 2025, and the February 2026 measures removed remote-access VPN equipment altogether.

how it surfaced

It surfaced as a stoppage. Asahi Breweries restarted production at all six of its domestic breweries from 2 October 2025, by the company’s notice of 8 October, while orders were handled partly by hand. Electronic ordering came back on 2 December 2025 for Asahi Group Foods and on 3 December for Asahi Breweries and Asahi Soft Drinks, according to the February 2026 notice. On 27 November 2025 the company told Reuters and AFP it aimed to bring logistics close to normal by February 2026. The Jaguar Land Rover page shows the same kind of halt at a carmaker.

The data side moved more slowly, and Asahi’s own statements on it are hard to square:

  • On 8 October 2025 Asahi said data suspected of unauthorised transfer had been found on the internet. The February 2026 notice says it reported to Japan’s Personal Information Protection Commission on 8 October and again on 10 December after finding such information online.
  • On 27 November 2025 its table listed people whose information may have been exposed: about 1,525,000 who had contacted customer service, plus telegram recipients, employees and their family members. Asahi’s four groups add up to about 1.9 million. Credit card data was not included.
  • On 18 February 2026 it listed information that had been exposed: 5,117 employees and retirees and 110,396 business partner contacts. The same notice says it had not confirmed publication of the personal information on its data center servers.
  • On 17 July 2026 it widened the list as a precaution, adding about 378,000 business partner contacts, while saying it had found no evidence that personal information on its data center servers was transferred out.

The same route appears elsewhere in this record. Colonial Pipeline shows a remote-access login that was enough on its own, and Ingram Micro shows how long the question of which records left can run after the systems are back.

A box at the edge of one site is a door into everything that site can reach, and the admin passwords behind it decide how far an intruder walks.

The guide on the box at the edge nobody owns covers the logins that live on those devices, and blast radius covers how to count what one administrator account can reach.

picture it at a company like yours

The company here is made up. The other two paths are not: they happened, and each links to the story.

your company
a normal dayA warehouse or branch reaches the head office systems through a small network box that someone set up years ago and that works without complaint.
the gap nobody seesNobody counts that box as a way in, and some admin passwords on the main servers have not changed since they were set.a password is the only lock
  1. in this story
    the day it mattersSomeone gets through the box, finds an admin password that gives way, and spends quiet evenings looking around before anything breaks.
    what it costs youOne morning every connected server is locked, orders go back to phone and paper, and customer records may have gone with them.
  2. or it goes like this
    howLeaked passwords are tried against customer accounts until some open.
    what leavespersonal details of customers and their contactswho ends up with itfraudsters
    it happened23andMe, 2023
  3. or it goes like this
    howAn old password opens a data store that never required a second step.
    what leavesthe whole database in one downloadwho ends up with itan extortion group
    it happenedThe Snowflake wave, 2024

sources

  1. Asahi Group Holdings: Notice of System Failure Due to Cyberattack, 29 September 2025
  2. Asahi Group Holdings: Update on System Disruption Due to Cyberattack (2nd), 3 October 2025
  3. Asahi Group Holdings: Update on System Disruption Due to Cyberattack (3rd), 8 October 2025
  4. Asahi Group Holdings: Update on System Disruption Due to Cyberattack (4th), 14 October 2025
  5. Asahi Group Holdings: Investigation Results and Future Measures on Cyberattack Data Exposure, 27 November 2025
  6. アサヒグループホールディングス: サイバー攻撃による情報漏えいに関する調査結果と今後の対応について, 27 November 2025 (Japanese)
  7. Asahi Group Holdings: Measures to Prevent Recurrence of System Disruption by a Cyberattack and Strengthening the Governance System, 18 February 2026
  8. アサヒグループホールディングス: サイバー攻撃被害の再発防止策とガバナンス体制の強化について, 18 February 2026 (Japanese)
  9. Asahi Group Holdings: Regarding Personal Information That May Have Been Exposed Due to a Cyberattack, 17 July 2026
  10. Reuters via Insurance Journal: Japan's Asahi Aims to Restore Logistics by February Following Cyberattack, 3 December 2025
  11. AFP via The Star: Beer giant Asahi not engaging with hackers after cyberattack, 27 November 2025

← all myths

your turn

what you can do about it

  1. this week

    List every remote-access box at every site, and switch off the ones nobody can name a reason for.

    Walk the sites with whoever runs your network and write down each VPN gateway, firewall and router that lets someone in from outside, with its owner and the systems it reaches. Asahi's first fix in February 2026 was to remove its remote-access VPN equipment altogether, and its second was to change passwords and tighten sign-in on every system. For each box you keep, check whether an admin account on your main servers could be reached from it with a password alone. Which of your sites could reach your servers on a quiet evening without anyone noticing?

  2. go deeper

  3. if you're not sure where to start

    Run the offboarding checklist on one leaver. It covers every account and token to close when someone leaves.

    open the checklist →

the letter · every two weeks

one access gap in your inbox, with the fix.

Every issue takes one way access creeps in, shows a real incident where it went wrong, and ends with one thing to check that week. Written for the people who run the tools, without a security team behind them.

  • 1one mechanism, explained plainly
  • 2one real incident, taken apart
  • 3one step you can take on Monday

get the next issue

One email every two weeks. Your address stays here and is never passed to vendors. One click to unsubscribe. Privacy.