---
title: "xz Utils backdoor discovery"
description: "What the retained public evidence establishes about the xz Utils backdoor 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/xz-utils-backdoor-discovery-2024"
markdown_url: "https://www.ally.security/incidents/xz-utils-backdoor-discovery-2024.md"
stix_url: "https://www.ally.security/incidents/xz-utils-backdoor-discovery-2024/stix.json"
---

# xz Utils backdoor discovery

Multi-year social engineering of a maintainer to insert an SSH backdoor into a core Linux compression library. Caught before widescale exploitation by a single engineer noticing a performance anomaly.

Last modified Sep 19, 2026 · 1 source

## Summary

- **Environment:** Open-source supply chain
- **Operational impact:** Caught before widescale exploitation by a single engineer noticing a performance anomaly
- **Financial impact:** No financial figure is established by the reviewed source evidence

## What happened

In 2024, xz Utils backdoor experienced an incident in its open-source supply chain environment. The retained source describes the attack path as follows: Multi-year social engineering of a maintainer to insert an SSH backdoor into a core Linux compression library. [1](#source-1)

The documented consequence was: Caught before widescale exploitation by a single engineer noticing a performance anomaly. [1](#source-1)

## Impact

- Documented impact: Caught before widescale exploitation by a single engineer noticing a performance anomaly. [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 retained source describes the attack path as follows: Multi-year social engineering of a maintainer to insert an SSH backdoor into a core Linux compression library. The canonical record does not add intrusion steps beyond those supported by the source. [1](#source-1)

### 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 [Backdoor in upstream xz/liblzma leading to ssh server compromise](https://www.openwall.com/lists/oss-security/2024/03/29/4). 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/xz-utils-backdoor-discovery-2024/stix.json>)

## Sources

Primary source records used to research this incident.

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

### Backdoor in upstream xz/liblzma leading to ssh server compromise

research · oss-security

<https://www.openwall.com/lists/oss-security/2024/03/29/4>

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

Review the supporting structured claims.

1. **Resulted In · 100% confidence · current**  
   xz Utils backdoor discovery: The reviewed source documents the xz utils backdoor discovery involving xz Utils backdoor.
2. **Resulted In · 83% confidence · current**  
   xz Utils backdoor discovery: Multi-year social engineering of a maintainer to insert an SSH backdoor into a core Linux compression library.
3. **Resulted In · 83% confidence · current**  
   xz Utils backdoor discovery: Caught before widescale exploitation by a single engineer noticing a performance anomaly.

</details>