--- title: "Boeing Named on INC Ransom Leak Site: What We Know" url: https://playciso.com/blog/boeing-inc-ransom-leak-site-claim updated: 2026-11-20 section: Blog publisher: PlayCISO --- # Boeing Named on INC Ransom Leak Site: What We Know > INC Ransom listed Boeing on its leak site on 20 Nov 2026, citing a Fort Campbell aircraft-support unit. Unverified: Boeing has not confirmed a breach. Source: https://playciso.com/blog/boeing-inc-ransom-leak-site-claim · Published: 2026-11-20 · Publisher: PlayCISO (https://playciso.com) Primary source: https://www.ransomware.live/group/incransom --- At **03:46 UTC on 20 November 2026** the ransomware tracker ransomware.live logged **Boeing** as a new victim on the **INC Ransom** leak site. Per the tracker's copy of the post, the group says the listing concerns **Boeing Sikorsky Aircraft Support (BSAS)**, an aircraft-support operation at Fort Campbell, Kentucky. **Boeing has not confirmed a breach.** It had made no public statement and filed no cybersecurity 8-K as of 20 November, and no reputable news outlet had reported or checked the claim. **Who this is for:** Boeing suppliers, customers and partners, defence-industrial-base security teams, and anyone asked "are we exposed?" when a prime contractor appears on a leak site. *Independent analysis. PlayCISO is not affiliated with Boeing. We did not visit the leak site; everything below comes from the tracker, company sources and outlets named in Sources. Facts as of 20 November 2026.* Confirmed vs not yet known **Confirmed:** a listing naming Boeing appeared on the INC Ransom leak site; ransomware.live logged it at 03:46 UTC on 20 November 2026. That is all that is confirmed. **Claimed, not verified:** that INC Ransom took data from Boeing Sikorsky Aircraft Support, including server contents and email archives. The post gives file counts, document descriptions and staff names; nobody independent has checked them, so we do not repeat them. **Not known:** whether any intrusion happened, at which entity, and what data, if any, was taken. Boeing had made no statement and filed no Item 1.05 (cybersecurity) 8-K as of 20 November; its latest 8-K, on 27 October, covers third-quarter results. No reputable outlet had reported the listing when we published. ## What INC Ransom claims The tracker's record headlines the post as a Boeing data breach, then narrows it: the group says the compromise is of **Boeing Sikorsky Aircraft Support (BSAS)** at Fort Campbell, Kentucky, which it calls a Boeing subsidiary under Boeing Global Services. It claims to hold the contents of several production servers and Microsoft 365 email archives, and it argues Boeing is responsible for the unit's security. The post also names individual staff; we do not. Two cautions. First, the corporate description is the group's. Boeing's own 1997 news release describes BSAS as "A Boeing and Sikorsky joint venture", supporting US Army special operations aviation at Fort Campbell. Who owns and runs its IT today is not something we could confirm, and it matters: a joint venture can sit outside a parent company's own network. Second, a big name at the top of a post about a smaller entity is a familiar extortion tactic. It draws attention and pressure. It does not show that Boeing's own systems were touched. The tracker shows no file sample or published data size for the entry, and the post threatens a phased release if Boeing does not engage. No date for it appears in the record we read. ## What Boeing says Nothing yet. Boeing's newsroom had no statement on a cyber incident as of 20 November (its latest release, on 15 November, is an aircraft order), and SEC EDGAR shows no Item 1.05 8-K. We will update this post if Boeing, a regulator or a reputable outlet says more. ## Who is INC Ransom? INC Ransom is a data-extortion and ransomware operation that emerged in **July 2023** and targets public and private organisations, including healthcare, education, government and industry, per BleepingComputer. It claimed the 2024 attack on NHS Dumfries and Galloway in Scotland, and took credit for a 2024 attack on Michigan's McLaren Health Care that forced dozens of surgeries to be cancelled (The Record). On **17 November 2026**, The Record reported that a 43-year-old man from Kazakhstan, described by prosecutors as part of an "8-Digits Team" working as an affiliate of the INC and Lynx ransomware strains, had been extradited from Italy and appeared in federal court in Tennessee. The Record also cites Palo Alto Networks and Group-IB: "INC either rebranded to Lynx or Lynx actors purchased the group's source code." The tracker lists more than 1,000 entries for INC Ransom, all of them claims. INC Ransom posted another notable entry an hour later: the tracker logged a listing under the domain **eni.it** at 04:42 UTC. Its text refers to agreements "with ENI", so it is unclear whether it concerns Eni itself or a company that deals with it; Eni has not confirmed anything and no reputable outlet has reported it. ## Boeing's earlier, separate incident (2023) Kept apart on purpose, because nothing reported connects it to this listing. In late October 2023 the LockBit ransomware gang listed Boeing. On 2 November 2023 Boeing confirmed to BleepingComputer: "We are aware of a cyber incident impacting elements of our parts and distribution business." It added: "This issue does not affect flight safety." LockBit later published files it said were taken from Boeing; SecurityWeek reported on 13 November 2023 that Boeing had confirmed parts of its distribution business were hit and said the incident did not threaten aircraft or flight safety. That incident was confirmed by Boeing; the 2026 INC Ransom listing is not. ## Timeline | When | What | Source | | --- | --- | --- | | Jan 1997 | Boeing describes BSAS as a Boeing and Sikorsky joint venture working at Fort Campbell | Boeing news release | | Jul 2023 | INC Ransom emerges | BleepingComputer | | 2 Nov 2023 | Boeing confirms a cyber incident in parts of its parts and distribution business after a LockBit claim (separate incident) | BleepingComputer | | Nov 2023 | LockBit publishes files it says were stolen from Boeing (separate incident) | SecurityWeek | | 27 Oct 2026 | Boeing's latest 8-K before the listing: third-quarter results (Items 2.02, 9.01) | SEC EDGAR | | 17 Nov 2026 | An alleged INC and Lynx affiliate is extradited to the US | The Record | | 20 Nov 2026, 03:46 UTC | Tracker logs Boeing as a new INC Ransom victim; the post names Boeing Sikorsky Aircraft Support | ransomware.live | | 20 Nov 2026, 04:42 UTC | Tracker logs an INC Ransom entry under the domain eni.it | ransomware.live | | 20 Nov 2026 | No Boeing statement in its newsroom; no Item 1.05 8-K; no reputable outlet coverage found | Boeing newsroom; SEC EDGAR (checked by PlayCISO) | ## What Boeing suppliers, customers and security leaders should do this week The useful work is the same whether this claim turns out real, overstated or empty. - Don't act on a screenshot. Ask your Boeing contracts, supplier-management or programme contact, in writing, whether they are aware of the claim and whether your data or access is in scope. Track Boeing's own statements and filings, not reposts. - Map what you share, and with which entity. List what Boeing and its joint ventures hold for you: drawings and technical data, contracts and pricing, supplier-portal accounts, quality records. The listing points at a joint venture, so check whether you deal with BSAS or similar ventures directly. The [vendor risk scorecard](/tools/vendor-risk-scorecard) helps rank them. - Know your export-control and contract clocks. If controlled technical data or defence contract information could be involved, find out now who in your company owns the reporting decision under your contracts and export licences. Defence suppliers should also confirm their own CMMC posture is current: the [CMMC SPRS score calculator](/tools/cmmc-sprs-score-calculator) is a quick check. - Rotate shared credentials. If any Boeing or joint-venture portal uses a shared or service account, or an API key you issued, rotate it and confirm MFA. Cheap, whatever the outcome. - Warn staff about lures. Big-name extortion news is reused in phishing ("Boeing supplier data leak: check your exposure"). Tell procurement, finance and engineering to expect it. - Get the third-party playbook out now. Who decides, who talks to customers and regulators, and on what clock, if a data set naming you is published. Walk it with the [third-party breach response checklist](/tools/third-party-breach-response-checklist) and log any supplier notice in [third-party breach intake](/tools/third-party-breach-intake). - Never download "leaked" data. If files are published, let legal and your incident responder decide how any review happens, especially where export-controlled material may be involved. For context on the other organisations named this week, see the [19 November leak-site roundup](/blog/ransomware-leak-site-claims-19-november-2026) and our write-ups on [NVIDIA and The Gentlemen](/blog/nvidia-the-gentlemen-leak-site-claim) and [AutoZone and Inception](/blog/autozone-inception-leak-site-claim). To rehearse being the name on the site yourself, run a scenario in the [Cyber War Room](/warroom). ## FAQ ### Has Boeing been hacked by INC Ransom? Not confirmed. The tracker ransomware.live logged Boeing as a new victim on the INC Ransom leak site at 03:46 UTC on 20 November 2026. Boeing had made no public statement about it as of 20 November, had filed no cybersecurity (Item 1.05) 8-K with the SEC, and no reputable news outlet had reported or checked the claim. A leak-site listing is a claim, not proof. ### What does INC Ransom say it took from Boeing? Per the tracker's copy of the post, the group says the listing concerns Boeing Sikorsky Aircraft Support (BSAS), an aircraft-support operation at Fort Campbell, Kentucky, and claims it took server contents and email archives. None of this has been verified, so we do not repeat the group's file counts, document descriptions or the staff it names. Boeing's own 1997 release describes BSAS as a Boeing and Sikorsky joint venture; the group calls it a Boeing subsidiary. ### Is this the same as the 2023 LockBit attack on Boeing? Nothing reported links them. In late 2023 LockBit claimed an attack on Boeing, and Boeing confirmed on 2 November 2023: "We are aware of a cyber incident impacting elements of our parts and distribution business." It added: "This issue does not affect flight safety." LockBit later published files it said were Boeing's. That incident was confirmed; this 2026 listing is not. ### Who is INC Ransom? A data-extortion and ransomware operation that emerged in July 2023 (BleepingComputer). It claimed the 2024 attack on NHS Dumfries and Galloway in Scotland and took credit for a 2024 attack on Michigan's McLaren Health Care (The Record). On 17 November 2026 The Record reported that a Kazakh man described by prosecutors as an affiliate of the INC and Lynx ransomware strains had been extradited from Italy to the US. ### Was Eni also named by INC Ransom? The tracker logged an INC Ransom entry under the domain eni.it at 04:42 UTC on 20 November 2026. The tracker's copy of the post refers to agreements "with ENI", so it is unclear whether it concerns Eni itself or a company that deals with it. Eni has not confirmed anything and no reputable outlet has reported it. Treat it as an unverified claim. ### I am a Boeing supplier or customer. What should I do? Do not act on a screenshot and never download anything said to be leaked. Ask your Boeing contracts or supplier-management contact, in writing, whether they are aware of the claim and whether your data is in scope. List what you share with Boeing and with its joint ventures (drawings, contracts, export-controlled technical data, portal accounts), rotate any shared credentials, warn staff about phishing that uses the news, and have your third-party breach playbook and any contractual or regulatory notification clocks ready in case the claim is substantiated. ## Sources All accessed 20 November 2026. We did not visit or link the leak site, and we reproduce no data from the post. - [ransomware.live: Boeing entry (INC Ransom)](https://www.ransomware.live/id/Qm9laW5nQGluY3JhbnNvbQ==) and [INC Ransom group page](https://www.ransomware.live/group/incransom) (tracker; Boeing discovered 20 Nov 2026 03:46 UTC, eni.it 04:42 UTC; read via the public API) - [Boeing newsroom: news releases and statements](https://boeing.mediaroom.com/news-releases-statements) (checked 20 Nov; no statement on a cyber incident) - [SEC EDGAR: The Boeing Company 8-K filings](https://www.sec.gov/cgi-bin/browse-edgar?action=getcompany&CIK=0000012927&type=8-K&dateb=&owner=include&count=40) (checked 20 Nov; latest 8-K 27 Oct 2026, Items 2.02 and 9.01; no Item 1.05) - [Boeing: Boeing Sikorsky submits bid on major U.S. Special Operations Command contract](https://boeing.mediaroom.com/1997-01-25-Boeing-Sikorsky-Submits-Bid-On-Major-U.-S.-Special-Operations-Command-Contract) (25 Jan 1997; describes BSAS as a Boeing and Sikorsky joint venture) - [BleepingComputer: Boeing confirms cyberattack amid LockBit ransomware claims](https://www.bleepingcomputer.com/news/security/boeing-confirms-cyberattack-amid-lockbit-ransomware-claims/) (Sergiu Gatlan, 2 Nov 2023; Boeing statement) - [SecurityWeek: Ransomware group leaks files allegedly stolen from Boeing](https://www.securityweek.com/ransomware-group-leaks-files-allegedly-stolen-from-boeing/) (Eduard Kovacs, 13 Nov 2023) - [BleepingComputer: INC Ransom threatens to leak 3TB of NHS Scotland stolen data](https://www.bleepingcomputer.com/news/security/inc-ransom-threatens-to-leak-3tb-of-nhs-scotland-stolen-data/) (Bill Toulas, 27 Mar 2024; group background) - [The Record: Kazakh ransomware hacking suspect extradited from Italy](https://therecord.media/kazakh-suspected-extradited-charges-8-digits-team-inc-lynx) (Jonathan Greig, 17 Nov 2026; INC and Lynx) *This is a developing story about an unverified claim. We will update it if Boeing, a regulator or a reputable outlet confirms more. General information, not legal or security advice.*