Skip to content
Breach Index · running record

Boeing ransomware claim (November 2026): what INC Ransom says and what is confirmed

On 20 November 2026 the INC Ransom extortion group listed Boeing on its leak site. Boeing has not confirmed a breach; Boeing did confirm a separate cyber incident in 2023.

Short answer

Was Boeing hacked by INC Ransom?

Not confirmed. INC Ransom named Boeing on its leak site on 20 November 2026 and, per a tracker’s copy of the post, says it concerns Boeing Sikorsky Aircraft Support at Fort Campbell, Kentucky, which Boeing has described as a Boeing and Sikorsky joint venture. Cybernews reports the group claims more than 3.6 million files from seven production servers and says the scope cannot be independently verified.

Boeing had made no public statement and filed no cybersecurity (Item 1.05) 8-K as of 22 November 2026. Separately, Boeing confirmed a cyber incident in its parts and distribution business in November 2023 after a LockBit claim.

Timeline at a glance

  1. 20 Nov 2026INC Ransom lists Boeing; the post names Boeing Sikorsky Aircraft Support. (ransomware.live)Unverified claim
  2. Nov 2026Cybernews reports the claim: 3.6M+ files from seven servers claimed, scope unverifiable. (Cybernews)Reported
  3. 2 Nov 2023Boeing confirms a cyber incident in parts of its parts and distribution business (LockBit claim). (BleepingComputer)Confirmed

Last updated November 22, 2026. Every entry is dated and linked to its source; claims by attackers are labelled as claims, never stated as fact.

Boeing’s security posture at the time

What Boeing publicly said about its security certifications and controls, how big it is, and how its shares moved, each tied to a source. A certificate covers a stated scope at a point in time; it is not a guarantee about every system. Reviewed 22 Nov 2026. Compare all 2026 breaches.

Security certifications publicly held

No public certification found.

No public SOC 2 or ISO 27001 certificate for Boeing was found on its own pages (checked 22 Nov 2026). Boeing’s supplier cybersecurity page lists ISO 27001/27002, the NIST Cybersecurity Framework and NIST SP 800-171 as frameworks for suppliers and explains CMMC; that is guidance, not a Boeing certificate. Certificate registries were not searched.

Size

Consolidated revenue not verified for this page (see Boeing’s latest 10-K)

Listing: NYSE: BA

Share price around the disclosure

No reliable report of a share-price move around the disclosure was found.

Boeing incident timeline, in detail

Confirmed = acknowledged by Boeing, a regulator filing or a court. Reported = credible reporting Boeing has not fully confirmed. Unverified claim = an attacker or leak-site claim.

20 Nov 2026Unverified claimExtortion claim

INC Ransom names Boeing, citing a Fort Campbell aircraft-support venture

What happened. INC Ransom listed Boeing on its leak site on 20 November 2026; per the tracker’s copy of the post, the group says it concerns Boeing Sikorsky Aircraft Support at Fort Campbell, Kentucky, which Boeing has described as a Boeing and Sikorsky joint venture. Cybernews reports the group claims more than 3.6 million files from seven production servers and says the scope cannot be independently verified. Boeing has not confirmed a breach.

Impact. Unconfirmed; no data has been verified and Boeing has made no statement. People or records affected: Not disclosed. The file count is the group’s claim, as reported by Cybernews.

Sources: Cybernews — Boeing data breach allegations put decades of data at risk · ransomware.live — Boeing entry (INC Ransom, tracker) · SEC EDGAR — The Boeing Company 8-K filings (no Item 1.05 as of 22 Nov 2026) · Boeing — Boeing Sikorsky bid release, 1997 (BSAS described as a joint venture) · BleepingComputer — Boeing confirms cyberattack amid LockBit ransomware claims (2023) · Boeing supplier cybersecurity page

Where the reports disagree

  • INC Ransom calls Boeing Sikorsky Aircraft Support a Boeing subsidiary; Boeing’s own 1997 release describes it as a Boeing and Sikorsky joint venture.

The pattern across the record

Certified, and still breached?

We found no SOC 2 or ISO 27001 certification published by Boeing. That does not prove it had none; it means none was public.

A claim is not a confirmation

This entry rests on an attacker or leak-site claim the company has not confirmed. Leak sites exaggerate, recycle old data and list victims to pressure them. Treat it as a reason to ask questions, not as an established breach.

What it means for Boeing Boeing suppliers, customers and partners — and what to do

What Boeing’s customers, partners and security teams can do now, based only on what has been disclosed.

  1. 1.Ask in writing, then wait for evidence

    Ask the company whether it is aware of the claim and whether any system holding your data is in scope. Do not act on leak-site screenshots alone.

  2. 2.Prepare, without assuming

    Check what data of yours the company holds so you can move fast if the claim is confirmed.

    Open the Third-Party Breach Intake
  3. 3.Watch for confirmation

    A filing, regulator notice or company statement is what turns a claim into a confirmed breach. This page will be updated if one appears.

Take this with you
Incident timeline · What Boeing Boeing suppliers, customers and partners should do · Sources

CISO takeaways

Sources

Company statements and regulator filings first, then reputable reporting. Reviewed November 22, 2026.

  1. 1.Cybernews — Boeing data breach allegations put decades of data at risk — Cybernews, reviewed 22 Nov 2026
  2. 2.ransomware.live — Boeing entry (INC Ransom, tracker) — ransomware.live (tracker), reviewed 22 Nov 2026
  3. 3.SEC EDGAR — The Boeing Company 8-K filings (no Item 1.05 as of 22 Nov 2026) — SEC EDGAR, reviewed 22 Nov 2026
  4. 4.Boeing — Boeing Sikorsky bid release, 1997 (BSAS described as a joint venture) — Boeing, reviewed 22 Nov 2026
  5. 5.BleepingComputer — Boeing confirms cyberattack amid LockBit ransomware claims (2023) — BleepingComputer, reviewed 22 Nov 2026
  6. 6.Boeing supplier cybersecurity page — Boeing, reviewed 22 Nov 2026

Frequently asked questions

Was Boeing hacked by INC Ransom?

Not confirmed. INC Ransom named Boeing on its leak site on 20 November 2026 and, per a tracker’s copy of the post, says it concerns Boeing Sikorsky Aircraft Support at Fort Campbell, Kentucky, which Boeing has described as a Boeing and Sikorsky joint venture. Cybernews reports the group claims more than 3.6 million files from seven production servers and says the scope cannot be independently verified.

Did Boeing have SOC 2 or ISO 27001 certification?

We found no SOC 2 or ISO 27001 certification published by Boeing. That does not prove it had none; it means none was public.

Is the 2026 INC Ransom claim the same as the 2023 LockBit attack on Boeing?

Nothing reported links them. Boeing confirmed the 2023 incident, saying on 2 November 2023 that it was aware of a cyber incident impacting elements of its parts and distribution business and that it did not affect flight safety. The 2026 INC Ransom listing is unconfirmed.

Our coverage of Boeing

Same sourced, verification-tagged timeline, company by company — compare how peers have fared.

Or see the full Breach Index and how to read it.

Independent analysis for security-leadership education; not affiliated with or endorsed by Boeing. Facts are attributed to the dated sources above, and anything disputed or unconfirmed is labelled as such. See the full Breach Index.