Air Canada was listed on 09 September 2026 by the thegentlemen ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). thegentlemen listed 105 organizations that month and 1119 in total.
- Listed 70 days ago.
- 874 organizations were listed by all groups in September 2026, see the month.
- 36 in Transportation that month.
- 29 in CA that month.
- 1 other listing for the same organization.
Updated 2026-11-14 15:46 UTC. Data: public leak-site listings. How we work.
Named in 2 separate listings
Another listing name this organization: a different group, or the same group months apart. Each is a claim the group published, not a confirmed breach. The same group listing it again within a few months is not counted: that is the same listing sent twice or moved from countdown to published.
Threat Group Post & Evidence
- Listed by
- Thegentlemen 1,119 listings in total
The listing states no data size and no ransom demand.
No capture of the original post
We only show a screenshot when we captured the group's own page ourselves. For this listing we have not, so none is shown.
What the group says it holds
Taken from the group's own post. Ransomware Tracker by ExposureDrift has not seen the data and cannot confirm any of this.
aircanada.com zoominfo.com/c/air-canada/3937344 Revenue $16.5 Billion Air Canada We have taken 51409 critical files! Canada's flag carrier and largest airline — founded in 1937 as Trans-Canada Air Lines, HQ'd in Montréal, ~37,000 employees, 45.3M passengers in 2025, and a founding Star Alliance member. Record revenue: $22.37B CAD in 2025 ($6.27B in Q2 2026 alone, +11%), but a fuel shock (+50.8% per litre) and $388M one-off charges pushed Q2 2026 to a $178M net loss — guidance cut, though load factor (87.5%) and Aeroplan (10M+ members), Cargo (+29%) and Sixth Freedom traffic stay strong. Its moat: the most aggressive fleet renewal in its history — A321XLRs with Canada's first lie-flat seats on a narrowbody, 787-10s and A350-1000s — unlocking "thin" long-haul routes no widebody could fly (Oslo, Shannon, Basel, Dubrovnik, Guangzhou) ahead of Super Bowl 2027 and the LA 2028 Olympics.
Amounts as written
- 37,000 employees
Kinds of data mentioned
-
Customer or client data
“…~37,000 employees, 45.3M passengers in 2025, and a founding Star Alliance member. Record revenue: $22.37B CAD in 2025 ($6.27B in Q2 2026 alone, +11%), but a fuel shock (+50.8%…”
-
Employee and HR records
“…— founded in 1937 as Trans-Canada Air Lines, HQ'd in Montréal, ~37,000 employees, 45.3M passengers in 2025, and a founding Star Alliance member. Record revenue: $22.37B CAD…”
-
Source code and designs
“…in 2025, and a founding Star Alliance member. Record revenue: $22.37B CAD in 2025 ($6.27B in Q2 2026 alone, +11%), but a fuel shock (+50.8% per litre) and $388M one-off…”
What to do about this listing
Choose who you are. Each step shows why it appears and, where we have one, its source. General guidance, not legal or incident-response advice.
If you work with Air Canada (customer, supplier or partner)
Within 3 days
- Do not open the group's page or download the data Do not visit the leak site or download files from a listing. Holding stolen data can be unlawful, and the files can carry malware. Wait for the company's own notice. Why: A safety rule for any leak listing.
- Ask Air Canada directly Write to your contact and ask whether your data, or your access to their systems, is in scope, and ask for a written statement. Your contract or data-protection law may oblige them to tell you if your data is affected: check the notification clause. Why: A listing is only the group's claim; the company is the one who can confirm what was taken.
- Review what Air Canada can reach of yours List the accounts, API keys, VPN or SSO connections and shared mailboxes this company has with you. Rotate the keys you gave them and remove access they do not need. Why: Access a supplier holds is how a listing about them can become a problem for you.
- Expect convincing phishing Messages that quote real orders, invoices or names are more likely after a leak. Tell finance and the help desk to treat any request from, or about, this company with extra care. Why: The post names: customer or client data, employee and hr records.
- Check software and integrations you take from them If you run their software or call their API, check that updates come through the usual channel and rotate the keys and tokens you hold for it. Why: The post names: source code and designs.
Within 30 days
- Keep watching Air Canada A supplier's listing can change after the first sighting: the group can add data, change the status or publish. Add the company to your supplier list to be told, and check your own domain too. Why: A listing is a moving claim, not a single event. Add to your supplier list Check your own domain
If you are Air Canada
First 24 hours
- Reset credentials and sessions Force password, API-key and session-token resets for the accounts the post suggests were exposed, enforce phishing-resistant MFA, and revoke OAuth/SSO grants issued before the listing date. Why: The post names: customer or client data.
Within 3 days
- Support affected individuals Identify the employees or customers whose identity data may be in scope and offer identity-protection or credit monitoring; brief the help desk on likely phishing. Why: The post names: employee and hr records.
- Rotate secrets and signing keys Assume secrets in repositories are exposed: rotate API keys, tokens and code-signing keys, and review build and release systems for unexpected changes. Why: The post names: source code and designs.
- Size the exposure against your own systems Inventory which systems hold data of the kind and volume claimed, so notification and legal decisions rest on your records rather than the group's figures. Why: The post claims: 37,000 employees. Treat group figures as unverified.
- Lock down exposed admin, VPN and SSO panels Restrict by IP allow-list or a zero-trust proxy and require MFA. Why: A passive scan found 1 critical panel(s) reachable from the internet.
- Retire staging and dev exposure Take non-production hosts off the internet or behind authentication, and rotate any secrets they held. Why: A passive scan found 1 non-production host(s) that are public.
- Check regulatory and stakeholder notification duties Canada: PIPEDA requires reporting breaches that pose a real risk of significant harm, as soon as feasible. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: Canada.
Within 30 days
- Check shared suppliers and software List the suppliers and software you share with other Transportation organizations and ask them whether they were affected. Why: thegentlemen listed 9 other Transportation organization(s) in the last 90 days.
General readiness for any ransomware claim (not about this listing)
- Offline, immutable backups and a restore drill Keep backups outside domain-admin reach and practise a restore; a leak does not remove the risk of re-encryption. Why: General practice for any ransomware claim; not specific to this listing.
- Look for mass file access and unusual outbound transfers Review EDR, proxy and identity logs for bulk reads, archive creation and large uploads to file-sharing services. Why: General practice for any ransomware claim; not specific to this listing.
- Phishing-resistant MFA on remote access Enforce MFA on VPN, SSO and admin panels, and retire password-only or SMS-based remote access. Why: General practice for any ransomware claim; not specific to this listing.
Listing details
Listing severity score (heuristic)
69/100 • ELEVATEDA heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.
External Attack Surface Profile
ASM IntelligenceRun a free passive scan on your own domain to see what an attacker can see from the outside.