Thought Leadership
Asahi Group Holdings is grappling with a severe IT security incident that has brought large portions of its Japan operations to a standstill. Orders and deliveries are completely suspended.
Asahi Group Holdings, manufacturer of Japan’s best-selling beer, has fallen victim to a cyberattack affecting multiple business divisions. According to the company’s statement, ordering and shipping processes have been completely halted. The call center and customer service are also currently unreachable.
Market leader experiences significant disruption
Asahi ranks among Japan’s largest breweries and holds approximately one-third of the domestic market share. The company employs around 30,000 people, produces 100 million hectoliters of beverages annually, and generated revenues of nearly $20 billion USD in 2024.
Internationally, the company operates through four regional branches (Japan, Europe, Oceania, and Southeast Asia) and holds well-known brands including Peroni, Pilsner Urquell, Grolsch, and Fullers in its portfolio through strategic acquisitions.
Only Japan operations affected
According to Asahi’s Japanese headquarters, only activities in Japan have been impacted by the attack. Whether data has been leaked or stolen remains unclear—investigations are still ongoing.
“Asahi Group Holdings, Ltd. is currently experiencing a system disruption caused by a cyberattack that is affecting operations in Japan,” reads a statement published today on the company’s website. “At this time, no leak of personal data or customer information to third parties has been confirmed.”
The company apologized to customers and business partners for the inconvenience.
Cause and perpetrators still unknown
Asahi is investigating the cause of the disruption and working to restore the affected systems, according to company statements. The company has not provided a timeline for resuming normal operations.
According to some sources, the attack began around 7:00 AM Japan time. Details about the attackers or the initial attack vector are unknown. To date, no ransomware group has publicly claimed responsibility for the incident.
