Boeing was listed on 20 November 2026 by the incransom ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). incransom listed 72 organizations that month and 1045 in total.
- Listed 0 days ago.
- 979 organizations were listed by all groups in November 2026, see the month.
- 23 in Government & Defense that month.
- 431 in US that month.
- 1 other listing for the same organization.
Updated 2026-11-20 04:29 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
- INC Ransom 1,045 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.
# THE BOEING COMPANY — DATA BREACH ## Boeing Sikorsky Aircraft Support (BSAS): Complete Compromise --- Boeing Sikorsky Aircraft Support — a Boeing subsidiary operating under Boeing Global Services at Fort Campbell, Kentucky — has been fully compromised. BSAS provides Life Cycle Contractor Support to the United States Special Operations Command's 160th Special Operations Aviation Regiment, the Night Stalkers — maintaining MH-6M Little Bird, MH-47G Chinook, and MH-60M Black Hawk helicopters for classified special operations worldwide. The breach encompasses the complete contents of seven production servers (FINSRVR19, PSQLSRVR19, PSQLHOST19, PSQLLAB19, DDRAWER1, DDRAWER2, DDRAWER3) — over 3.6 million files and thirty-three years of operational data from 1993 through October 2026. Additionally, Microsoft 365 email archives have been obtained for dozens of personnel including the General Man…
Show the full post (12874 characters)
# THE BOEING COMPANY — DATA BREACH ## Boeing Sikorsky Aircraft Support (BSAS): Complete Compromise --- Boeing Sikorsky Aircraft Support — a Boeing subsidiary operating under Boeing Global Services at Fort Campbell, Kentucky — has been fully compromised. BSAS provides Life Cycle Contractor Support to the United States Special Operations Command's 160th Special Operations Aviation Regiment, the Night Stalkers — maintaining MH-6M Little Bird, MH-47G Chinook, and MH-60M Black Hawk helicopters for classified special operations worldwide. The breach encompasses the complete contents of seven production servers (FINSRVR19, PSQLSRVR19, PSQLHOST19, PSQLLAB19, DDRAWER1, DDRAWER2, DDRAWER3) — over 3.6 million files and thirty-three years of operational data from 1993 through October 2026. Additionally, Microsoft 365 email archives have been obtained for dozens of personnel including the General Manager, CFO, Facility Security Officer, Contracts Manager, Finance, IT, Accounts Payable, and operational staff. Boeing personnel serve as CFO (Michael Harris — "Boeing Sr. Finance Manager"), IT Lead (Daryl Armstrong), and General Counsel (Ben Tyson) at BSAS Board level. Boeing bears direct and undeniable responsibility for the cybersecurity of this operation. --- ## 1. THE $706.5 MILLION CONTRACT The Board of Directors presentation from **Meeting #40, October 8, 2026** — marked "BSAS Proprietary" on every page — has been obtained in full. It contains the complete BSAS 2.0 follow-on contract proposal to USSOCOM: | Period | Costs | Fee | Total Value | Profit | |--------|-------|-----|-------------|--------| | Base 2027 | $151.1M | $17.1M | $168.2M | 11.29% | | Option 1 2028 | $148.1M | $16.8M | $164.9M | 11.32% | | Option 2 2029 | $158.6M | $17.8M | $176.4M | 11.22% | | Option 3 Jan-Jun 2030 | $87.6M | $9.7M | $97.3M | 11.12% | | Option 4 Jul-Dec 2030 | $89.8M | $10.0M | $99.8M | 11.13% | | **Total** | **$635.2M** | **$71.4M** | **$706.5M** | | Thirty-eight CLINs spanning every aspect of the operation: LCCS labor, sustaining engineering, spares and repairs by platform (MH-6: $8.7M/yr, MH-47: $12.6M/yr, MH-60: $8.7M/yr), field service representatives, technical publications, travel, UK FMS CONUS and OCONUS support, FMS engineering, FMS spares, FMS special projects, and ODCs. Fee structure: FFP at 12% for labor and 15% for procurement, CPFF at 9.5%. Board-approved negotiation ranges: FFP 11-15%, CPFF 8-10%. The proposal was delivered to USSOCOM (TAKO) on June 1, 2026. On-site negotiations were scheduled for **October 20-23, 2026** — the precise timeframe of this breach. Sub Final Proposal Revisions due November 2, Boeing/BSAS FPR due to TAKO November 13, 2026. The BoD presentation also documents Boeing's negotiation strategy: removal of the Reliability Analysis requirement from the PWS, addition of $134M to Procurement and Special Task CLINs, removal of UK FMS FSR (relying on reach-back support), and a PoP change from 3.5 years to a 4-year base with option years. Anticipated negotiation topics include profit/fee alignment with current levels, salary substantiation for Leed personnel to "build a more competitive salary plan to stabilize workforce," FMS OCONUS staffing analysis by DCAA, and FMS flight hour adjustment methodology. Any competitor with access to this data can exactly replicate and underbid Boeing. Publication of this material ends Boeing's position on a $706.5 million contract. --- ## 2. CURRENT FINANCIAL PERFORMANCE From the same October 2026 Board presentation: **CY2026 (through September, with full-year estimate):** - Revenue: $134.57M (plan: $136.04M) - COGS: $119.22M - Gross Profit: $15.35M (11.40% margin) - EBIT: $13.10M (9.74% margin) - Total Assets: $22.13M - Owners Equity: $11.87M - DSO: 35.84 days / DPO: 19.42 days 2025 earnings distributions to Boeing and Lockheed Martin were paid May and August 2026. All 2026 CLINs fully funded except Sustaining Engineering at 67.8%. Additional $2M received for Spares & Repairs O&M. **Historical:** Net earnings 1993-2004: $22 million cumulative. Partner capital (2010): Boeing $4,151,361, Sikorsky $2,868,183. Monthly closing packages exist for every month January 2020 through September 2026. Audited financial statements from SRH CPAs for every year 1993 through 2024. Tax returns with EIN, bank routing number 293130837, Positive Pay check files documenting every vendor payment 2024-2025. DFAS government payment of $4,418,884.28 received October 6, 2026. Wire Transfer Authorizations and ACH documents present. --- ## 3. USSOCOM CONTRACTS AND CLASSIFIED MATERIALS **Current Contract:** IDIQ H92241-19-D-0003, fully executed with all sixteen modifications through P00016 (June 2024). - **DD Form 254** — Security Classification Specification (March 2024). Defines classified information handling, controlled under DoD 5220.22-M. - **Performance Work Statement** — Complete scope of Boeing/BSAS maintenance, logistics, repair, and sustainment for all SOCOM rotary-wing aircraft at Fort Campbell and remote sites (Hunter Army Airfield GA, Fort Lewis WA). - **CDRLs A001-A007** — RAM reports, Safety Assessments, Functional Hazard Analyses, technical publications. - **39+ Delivery Orders** with executed contracts, SOWs, proposals, and pricing: - **JSECST** — Joint Special Operations Electronic Combat Simulation Trainer. SOW describes electronic warfare training capabilities used by SOCOM crews. - **Eclypse AWTS** — Air Weapons Training System. Weapons simulation specifications. FFP pricing 2020-2025. - **AI Data Analysis** — Artificial intelligence for USSOCOM tactical purposes. PeopleTec subcontract. - **CAN ECUIC** — MH-47G Electronic Control Unit. Triumph Engine Control Systems. Engineering proposals, Data Rights Assertions, EMC-100 ECU specifications. - **FADEC Training** — Digital engine control systems for SOCOM helicopters. - **Material availability rates** — 93.87% Critical, 90.41% Non-Critical (FY24). Unit readiness posture exposed. - **64,800+ material transactions per year** — complete parts flow for 160th SOAR. - **Forward Pricing Rate Proposal CY2027-2030** — submitted to DCAA April-June 2026 — every labor rate, overhead, G&A, escalation factor for the next four years. - **Negotiated Cost Model 2019-2025** (24.5MB) — the complete historical pricing agreement. --- ## 4. UK FOREIGN MILITARY SALES — ITAR The breach includes the complete UK FMS program for 14 MH-47ER aircraft for UK Special Forces: - Pre-Phase 1 (H92241-23-F-0033) and Phase 1 (H92241-23-F-0071) — fully executed contracts. - Board of Directors discussions document the operational timeline: first two MH-47ER aircraft arriving Fort Campbell February-April 2027 for SIQ (Service Interoperability Qualification), testing the "14/83 concept." First aircraft to RAF Odiham, UK in February 2028. UK needs minimum three aircraft by April 2028 for "ready to train" requirement. - Odiham infrastructure described as "not going to plan" — developing contingencies for temporary Mil-Van setup. On-site survey scheduled December 2026. - Technical Assistance Agreement (TAA) being drafted through Boeing Trade Controls and Reliant Defense. Strategic Shipping identified for UK transactions. Nashville customs broker being sourced. - ITAR-controlled parts shipments and UK visitor coordination documented through October 2026 in email archives. All of this data is controlled under ITAR (22 CFR 120-130). Unauthorized disclosure to non-U.S. persons carries criminal penalties of up to $1 million per violation and 20 years imprisonment. --- ## 5. BOEING DEFENSE SUPPLY CHAIN - **1,039 vendor records** with payment volumes and federal Tax Identification Numbers. Top vendors: M.D. Helicopters ($8.3M), Triumph Engine Control ($5.8M), Pinnacle Solutions ($5.3M), Honeywell International ($4.3M), Keystone Turbine ($2.7M). - **Subcontractor CAGE/DUNS codes:** Boeing Mesa (8V613), Boeing Philadelphia (77272), Sikorsky Aircraft (78286), Rolls Royce (63005), Honeywell (02LU7), Raytheon (1Z436), MD Helicopters (1KVX4). - **Pentagon2000 ERP live database** — complete parts catalog, purchase order history, vendor master data for SOCOM helicopter maintenance. - **Positive Pay check files** (2024-2025) — every vendor payment with check numbers, amounts, payees. Single payments exceeding $460,000. - **Accounts Payable email archive** (29,850 messages, 2017-2026) — complete payment correspondence, remittance data, and vendor banking details. - **Employee Turnover Log** — complete record of departures and reasons. --- ## 6. BOEING KNEW AND FAILED TO ACT The email archive documents a seven-year pattern of known security failures that Boeing was warned about and chose not to fix: **May 2019** — BSAS Accounts Payable email compromised, malware distributed to vendors. Staff acknowledged: *"we were hacked last week."* No systemic security improvements followed. **December 2024** — Boeing Vulnerability Management (Kevin Miller) warned BSAS of *"targeted brute force attacks on subsidiaries perimeter"* and requested SonicWall log review. **January 2025** — Boeing distributed a Critical advisory for **CVE-2025-23006** affecting SonicWall SMA1000 — the exact model deployed at BSAS (serial 18C24177F990, hostname bsas2700). **September 2025** — Multi-Factor Authentication finally enabled on Microsoft 365 — after **six years** of operating without MFA. Until this date, every email account was protected by password alone. **January 2026** — First Access Control Policy created. Boeing IT Lead described it as *"the first one to be uploaded."* For seven years prior, there was no formal access control policy. **May 2026** — A Disaster Recovery Plan meeting was scheduled and immediately cancelled. No DR plan was ever completed. **August 2026** — One IT administrator (Daryl Armstrong) was granted M365 Global Administrator role — single point of failure for the entire tenant. **October 5, 2026** — Initial Engagement Meeting with Redspin (CMMC C3PAO). Assessment confirmed for April 2027. **October 2026** — Complete breach. Boeing was preparing for a security certification while operating without basic security controls. --- ## 7. CMMC CERTIFICATION — DEAD ON ARRIVAL Boeing/BSAS engaged Redspin for CMMC Level 2 certification. The assessment schedule was confirmed October 5, 2026: scoping call March 8, 2027; document submission April 5; Phase 1 assessment April 19-23; Phase 2 validation April 26-30; outbrief May 24, 2027. The assessment requires System Security Plans, Network Architecture Diagrams, Policy Documents, and evidence of compliance across 320 security objectives. These documents are now in our possession. The network they describe has been fully compromised. Boeing/BSAS cannot pass a CMMC assessment when their entire infrastructure has been exfiltrated during the preparation phase. Redspin will be obligated to report the compromise once informed. Without CMMC certification, Boeing is disqualified from the $706.5M BSAS 2.0 contract. --- ## 8. REGULATORY CONSEQUENCES - **DFARS 252.204-7012** — Failure to safeguard CUI. Financial data was marked [CUI] starting April 2026 — Boeing acknowledged its controlled status, then lost it. Mandatory 72-hour reporting to DoD CIO. - **ITAR (22 CFR 120-130)** — UK FMS data for 14 MH-47ER aircraft is export-controlled. Criminal penalties up to $1M per violation, 20 years. - **CMMC Level 2** — Automatic failure. Disqualification from $706.5M BSAS 2.0. - **15-year sole-source J&A** — Boeing's exclusive position could be revoked. - **DCAA MAAR 13 audit** (Assignment 2024K10320001) — Active audit would expand into information security investigation. - **Boeing Reputational** — Congressional scrutiny following 737 MAX and whistleblower cases. A SOCOM data breach at a Boeing subsidiary adds to the pattern of systemic failures across Boeing programs. --- ## 9. WHAT HAPPENS NEXT If Boeing does not engage in a cooperative resolution: - Phased release beginning with financial records and personnel data, then email correspondence, then contract documents and Board strategy materials. - Notification to DCAA, DCMA, and USSOCOM Contracting Officer (TAKO) regarding the breach scope and Boeing's failure to report. - Notification to Redspin that CMMC assessment materials are compromised. - Notification to UK Ministry of Defence regarding ITAR FMS data exposure. - Direct notification to Boeing Corporate Security and Lockheed Martin Corporate Security. - Public release of BSAS 2.0 complete proposal ($706.5M), Forward Pricing Rates 2027-2030, and Boeing's Board-approved negotiation strategy. - Publication of the seven-year email timeline documenting Boeing's knowledge of security failures and inaction. - Submission to defense industry media covering Boeing security, DoD contractor accountability, and SOCOM operations security.
Amounts as written
- 365 email
- 24.5MB
Kinds of data mentioned
-
Tax records
“…Audited financial statements from SRH CPAs for every year 1993 through 2024. Tax returns with EIN, bank routing number 293130837, Positive Pay check files documenting every…”
-
Accounting and ledgers
“…J&A** — Boeing's exclusive position could be revoked. - **DCAA MAAR 13 audit** (Assignment 2024K10320001) — Active audit would expand into information security investigation.…”
-
Banking and wire details
“…SRH CPAs for every year 1993 through 2024. Tax returns with EIN, bank routing number 293130837, Positive Pay check files documenting every vendor payment 2024-2025. DFAS…”
-
Payroll and salaries
“…Anticipated negotiation topics include profit/fee alignment with current levels, salary substantiation for Leed personnel to "build a more competitive salary plan to stabilize workforce,"…”
-
Passwords and credentials
“…operating without MFA. Until this date, every email account was protected by password alone. **January 2026** — First Access Control Policy created. Boeing IT Lead described it…”
-
Email and communications
“…operational data from 1993 through October 2026. Additionally, Microsoft 365 email archives have been obtained for dozens of personnel including the General Manager, CFO, Facility…”
-
Employee and HR records
“…Additionally, Microsoft 365 email archives have been obtained for dozens of personnel including the General Manager, CFO, Facility Security Officer, Contracts Manager, Finance,…”
-
Contracts and legal files
“…personnel including the General Manager, CFO, Facility Security Officer, Contracts Manager, Finance, IT, Accounts Payable, and operational staff. Boeing personnel serve as CFO…”
-
Databases and backups
“…(02LU7), Raytheon (1Z436), MD Helicopters (1KVX4). - **Pentagon2000 ERP live database** — complete parts catalog, purchase order history, vendor master data for SOCOM helicopter…”
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 Boeing (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 Boeing 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 Boeing 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: email and communications, passwords and credentials, employee and hr records.
- Verify payment-detail changes by phone Confirm any change to bank details or any urgent invoice with a number you already hold, not one in the message. Why: The post names: banking and wire details, payroll and salaries, accounting and ledgers, tax 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: databases and backups.
Within 30 days
- Keep watching Boeing 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 Boeing
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: passwords and credentials, email and communications, payroll and salaries.
- Protect payments Tell your bank, verify any change to supplier or payroll bank details by calling a known number, and watch for invoice-fraud emails that use real names and amounts. Why: The post names: banking and wire details, payroll and salaries, accounting and ledgers.
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 database and cloud access Rotate database and cloud-storage keys, review public bucket and snapshot sharing, turn on object-level audit logging and keep backup encryption keys separate. Why: The post names: databases and backups.
- Check for mailbox compromise Audit mailbox rules, forwarding and delegated access, rotate mail-admin credentials and move DMARC to p=reject to limit follow-on phishing. Why: The post names: email and communications.
- 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: 365 email, 24.5MB. Treat group figures as unverified.
- Check regulatory and stakeholder notification duties United States: state breach-notification laws apply; listed companies may also have SEC Form 8-K Item 1.05 duties for material incidents, and HIPAA applies to health data. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: United States.
Within 30 days
- Review privileged and contract material Ask counsel which contracts and privileged files are named, and whether client or partner confidentiality terms oblige you to tell them. Why: The post names: contracts and legal files.
- Watch for tax-filing fraud Tell your tax advisers and, where available, tax authorities so fraudulent filings made with exposed identifiers can be caught early. Why: The post names: tax records.
- Check shared suppliers and software List the suppliers and software you share with other Government & Defense organizations and ask them whether they were affected. Why: incransom listed 6 other Government & Defense 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)
100/100 • CRITICALA 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.