AstraZeneca Data Breach Allegedly Claimed by LAPSUS$ as Internal Data Access Reported
On March 20, 2026, the hacking group known as LAPSUS$ allegedly claimed responsibility for a data breach involving AstraZeneca. The attackers are reportedly offering a 3GB internal data dump for sale, suggesting a compromise of AstraZeneca's internal…
On March 20, 2026, the hacking group known as LAPSUS$ allegedly claimed responsibility for a data breach involving AstraZeneca. The attackers are reportedly offering a 3GB internal data dump for sale, suggesting a compromise of AstraZeneca's internal network.
The group has transitioned from public extortion to a pay-to-access model, seeking potential buyers through secure messaging applications for private negotiations. Currently, no full leak of the data is publicly available for free, indicating the group's financial motives through private sale.
The 3GB data dump reportedly includes sensitive intellectual property and infrastructure configuration details. Initial assessments suggest the data structure aligns with genuine enterprise exports related to internal identity and access management systems.
Source Code: Compromised components include Java Spring Boot applications, Angular frontend frameworks, and Python scripts. Cloud Infrastructure: Compromised components include Terraform configurations for AWS and Azure environments and Ansible roles for automation and orchestration. Secrets and Access: Compromised components include private cryptographic keys, Vault credentials, and authentication tokens related to GitHub and Jenkins CI/CD pipelines.
On March 20, 2026, the hacking group known as LAPSUS$ allegedly claimed responsibility for a data breach involving AstraZeneca.
The exposed directory tree reveals a root folder named AZU_EXFIL , containing a critical supply-chain portal repository identified as als-sc-portal-internal . This internal portal appears to manage essential logistical functions necessary for pharmaceutical distribution, including forecasting, inventory tracking, product master data management, SAP system integration, and OTIF delivery metrics.
The exposure of such detailed operational data could have significant implications for AstraZeneca’s internal supply chain operations, particularly with the presence of high-level privilege accounts across multiple internal repositories. These factors elevate the risk of privilege escalation and further mapping of the corporate environment.
As of the date of this report, AstraZeneca has not made any official statement regarding the alleged breach. Security researchers continue to monitor the situation closely due to the potential risk of further unauthorized access or secondary attacks against the organization.
Based on reporting by GBHackers.
