Incident BriefingsSamsung security incident

Samsung security incident

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

Last modified

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
  • Record status: Developing record. Reviewed September 19, 2026; updated as evidence emerges.

What happened

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

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

Impact

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

Timeline

  1. Documented public update

    The Samsung confirms hackers stole Galaxy devices source code records the incident facts used in this briefing.

    [1]

  2. 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]

Actors

  • Lapsus$ — identified in the supported attack description. [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. Details absent from that evidence are left unresolved rather than inferred. [1]