People search ALS Limited data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 2 ALS Limited-linked incidents. This page maps every attested event through 2026 with internal links to canonical records.
Why ALS Limited breach history matters
ALS Limited operates in Technology (Australia). Across indexed rows, recurring themes include ransomware and extortion, third-party and supply-chain exposure, unverified actor or scraping claims. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2026 — Aurora ransomware leak-site listing (unverified)
Unverified claim — treat actor counts cautiously. Unverified Aurora extortion claim — June 2026. On June 19, 2026 the Aurora ransomware group listed ALS Global / ALS Limited (ASX: ALQ), a testing, inspection, and certification company with operations in 65+ countries, claiming unauthorised access to IT systems and compromise of employee information, business documents, and proprietary research data. Malware.news and threat-intelligence aggregators reproduced the actor statement referencing ALS Limited's scale; ALS had not issued a matching public breach notice at Exposed categories include Actor marketing cites unauthorised IT access at global testing/inspection/certification firm ALS Limited (alsglobal.com)—employee, business document, and research data categories c. No attested victim count is published for this row yet. See the als-limited-aurora 2026 record and canonical BreachHistory entry.
2026 — unauthorized third-party access to IT systems; operations disruption (May)
Cataloged incident. ALS Limited (ASX: ALQ) disclosed malicious cyber activity involving unauthorized third-party access to portions of its IT environment around May 4 2026, with most laboratory and operational services restored shortly thereafter per Reuters and the company’s cyber incident microsite. ALS stated forensic partners were analyzing whether personal or sensitive commercial data were exfiltrated and promised regulatory notifications if required. BreachHistory mirrors the ASX-listed disclosure while keeping recordsAffected a Exposed categories include Under review per company statements—categories not finalized at initial cataloging. No attested victim count is published for this row yet. See the als-limited-cyber-incident-may 2026 reco and canonical BreachHistory entry.
Patterns and analysis
- Ransomware and extortion — appears across multiple ALS Limited catalog entries; prioritize controls that address this class of failure.
- Third-party and supply-chain exposure — appears across multiple ALS Limited catalog entries; prioritize controls that address this class of failure.
- Unverified actor or scraping claims — appears across multiple ALS Limited catalog entries; prioritize controls that address this class of failure.
- Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
- 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.
What to do if you may be affected
- Step 1: Enable phishing-resistant MFA on every account tied to this brand.
- Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
- Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
- Step 4: Review OAuth app permissions and revoke unused third-party integrations.
- Step 5: Bookmark the ALS Limited company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/als-limited · Latest: als-limited-aurora2026.
Sources: BreachHistory catalog (2 rows for ALS Limited), company and regulator disclosures cited in individual breach records.