---
title: "Boeing security incident"
description: "What the retained public evidence establishes about the Boeing incident, its attack path, impact, and response."
incident_type: "Cybersecurity incident"
status: "active"
last_modified: "2026-09-19"
canonical_url: "https://www.ally.security/incidents/boeing-security-incident-2023"
markdown_url: "https://www.ally.security/incidents/boeing-security-incident-2023.md"
stix_url: "https://www.ally.security/incidents/boeing-security-incident-2023/stix.json"
---

# Boeing security incident

The retained public source documents this consequence of the Boeing incident: Parts/distribution business data stolen and leaked.

Last modified Sep 19, 2026 · 1 source

## Summary

- **Environment:** Aerospace
- **Operational impact:** Parts/distribution business data stolen and leaked
- **Financial impact:** No financial figure is established by the reviewed source evidence

## What happened

The reviewed public record documents a cybersecurity incident involving Boeing in 2023. It does not establish the initial access path with enough specificity to describe it here. [1](#source-1)

The documented consequence was: Parts/distribution business data stolen and leaked. [1](#source-1)

## Impact

- Documented impact: Parts/distribution business data stolen and leaked. [1](#source-1)
- No financial loss, ransom amount, recovery cost, or regulatory penalty is established by the reviewed source evidence.

## Threat Group & Attack Vector

The reviewed source does not establish a sufficiently specific initial-access vector. The article therefore does not infer credentials, malware, a vulnerability, or a social-engineering path.

### Actors

- No threat actor group has been identified in the reviewed public evidence.

### TTPs

- No specific MITRE ATT\&CK technique is currently mapped for this case.

## Response

The reviewed source does not describe containment, notification, or restoration steps in enough detail to summarize them responsibly.

This account is bounded to [Boeing 2023 Form 10-K](https://www.sec.gov/Archives/edgar/data/12927/000001292724000010/ba-20231231.htm). Details absent from that evidence are left unresolved rather than inferred. [1](#source-1)

## Assets

[Download the case-scoped STIX 2.1 bundle](<https://www.ally.security/incidents/boeing-security-incident-2023/stix.json>)

## Sources

Primary source records used to research this incident.

<a id="source-1"></a>

### Boeing 2023 Form 10-K

regulatory · The Boeing Company

<https://www.sec.gov/Archives/edgar/data/12927/000001292724000010/ba-20231231.htm>

<details>
<summary>Evidence ledger</summary>

Review the supporting structured claims.

1. **Resulted In · 100% confidence · current**  
   Boeing security incident: The reviewed source documents the boeing security incident involving Boeing.
2. **Affected Organization · 100% confidence · current**  
   Boeing security incident: Boeing
3. **Resulted In · 88% confidence · current**  
   Boeing security incident: Parts/distribution business data stolen and leaked.

</details>