---
title: "Samsung security incident"
description: "What the retained public evidence establishes about the Samsung 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/samsung-security-incident-2022"
markdown_url: "https://www.ally.security/incidents/samsung-security-incident-2022.md"
stix_url: "https://www.ally.security/incidents/samsung-security-incident-2022/stix.json"
---

# Samsung security incident

Lapsus$. approximately 190GB source code (Galaxy devices, Knox) stolen.

Last modified Sep 19, 2026 · 1 source

## Summary

- **Environment:** Electronics/Tech
- **Operational impact:** approximately 190GB source code (Galaxy devices, Knox) stolen
- **Financial impact:** No financial figure is established by the reviewed source evidence

## What happened

In 2022, Samsung experienced an incident in its electronics/tech environment. The retained source describes the attack path as follows: Lapsus$. [1](#source-1)

The documented consequence was: approximately 190GB source code (Galaxy devices, Knox) stolen. [1](#source-1)

## Impact

- Documented impact: approximately 190GB source code (Galaxy devices, Knox) stolen. [1](#source-1)
- No financial loss, ransom amount, recovery cost, or regulatory penalty is established by the reviewed source evidence.

## Timeline

### March 7, 2022 — Documented public update

The [Samsung confirms hackers stole Galaxy devices source code](https://www.bleepingcomputer.com/news/security/samsung-confirms-hackers-stole-galaxy-devices-source-code/) records the incident facts used in this briefing. [1](#source-1)

### September 19, 2026 — Briefing updated

This briefing was last reviewed and updated on September 19, 2026.

## Threat Group & Attack Vector

The retained source describes the attack path as follows: Lapsus$. The canonical record does not add intrusion steps beyond those supported by the source. [1](#source-1)

### Actors

- **Lapsus$** — identified in the supported attack description. [1](#source-1)

### 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 [Samsung confirms hackers stole Galaxy devices source code](https://www.bleepingcomputer.com/news/security/samsung-confirms-hackers-stole-galaxy-devices-source-code/). 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/samsung-security-incident-2022/stix.json>)

## Sources

Primary source records used to research this incident.

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

### Samsung confirms hackers stole Galaxy devices source code

news · BleepingComputer

<https://www.bleepingcomputer.com/news/security/samsung-confirms-hackers-stole-galaxy-devices-source-code/>

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

Review the supporting structured claims.

1. **Resulted In · 95% confidence · current**  
   Samsung security incident: Lapsus$.
2. **Resulted In · 84% confidence · current**  
   Samsung security incident: approximately 190GB source code (Galaxy devices, Knox) stolen.
3. **Occurred At · 100% confidence · current**  
   Documented public update: 2022-03-07
4. **Affected Organization · 100% confidence · current**  
   Samsung security incident: Samsung
5. **Resulted In · 100% confidence · current**  
   Samsung security incident: The reviewed source documents the samsung security incident involving Samsung.

</details>