Skip to main content
Mallory
Malware1 associated actor1 associated CVE

XZ Utils backdoor

Tracked since Mar 18, 2026 · Updated 8 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
Vulns1Associated
Actors1Associated
ATT&CK9Techniques
IOCs0Tracked
Is this in your environment?See whether this family's indicators match your telemetry and which of your assets are exposed to the CVEs associated with it.
Check your exposure
Associated CVEs

Associated vulnerabilities

1 CVE Mallory has correlated with this family across public research and vendor advisories. Each card links to the full Mallory page for that vulnerability.

CVE-2024-3094via malware newsXZ Utils BackdoorThe XZ Utils backdoor was a deliberately hidden piece of malicious code planted in versions 5.6.0 and 5.6.1 of the xz compression library, designed to let a remote attacker bypass SSH authentication on affected Linux systems.View vulnerability →Source ↗
Threat actors

Associated threat actors

1 distinct threat actor Mallory has associated with this family across public reporting. Open in Mallory to see the full evidence chain and overlapping campaigns.

View more details →
Jia Tan

The XZ Utils backdoor was a deliberately hidden piece of malicious code planted in versions 5.6.0 and 5.6.1 of the xz compression library, designed to let a remote attacker bypass SSH authentication on affected Linux systems.

via malware newsmalware.news
MITRE ATT&CK

Techniques & procedures

9 distinct techniques documented for this family, organized by ATT&CK tactic.

Initial Access

2 techniques
T1195Supply Chain CompromiseEvidence1

Red Hat is now tracking this supply chain security issue as CVE-2024-3094... The malicious code is obfuscated and can only be found in the complete download package, not in the Git distribution, which lacks the M4 macro, which triggers the backdoor build process.

T1195.001Compromise Software Dependencies and Development ToolsEvidence1

Malicious code was found in XZ source packages beginning with release 5.6.0; a concealed test file is used during the liblzma compilation process to extract a precompiled object file and alter liblzma functions.

Execution

3 techniques
T1059Command and Scripting InterpreterEvidence1

If the payload successfully passes verification steps and signature checks, it is then transferred to libc's system() function. This function is designed to execute the payload.

T1574Hijack Execution FlowEvidence1

If the malicious macro is present, the second-stage artifacts found in the Git repository are injected during the build time.

T1574.006Dynamic Linker HijackingEvidence1

The script mainly aims to modify the MakeFile of liblzma in order to interfere with its symbol resolution process in runtime, particularly causing the RSA_public_decrypt symbol to point to its own malicious backdoor code.

Stealth

4 techniques
T1027Obfuscated Files or InformationEvidence2

Through a series of complex obfuscations, a concealed test file within the source code is used during the liblzma compilation process to extract a precompiled object file.

T1036MasqueradingEvidence1

After performing the command sent by the attacker, the backdoor replaces the public RSA key object with a prebuilt constant key; alternatively, it replaces log entries describing successful connections with entries describing failed connection attempts.

T1574Hijack Execution FlowEvidence1

If the malicious macro is present, the second-stage artifacts found in the Git repository are injected during the build time.

T1574.006Dynamic Linker HijackingEvidence1

The script mainly aims to modify the MakeFile of liblzma in order to interfere with its symbol resolution process in runtime, particularly causing the RSA_public_decrypt symbol to point to its own malicious backdoor code.

Lateral Movement

1 technique
T1021.004SSHEvidence1

During the public key authentication process of sshd, the RSA_public_decrypt function gets called, causing the attacker's code to be executed. This code attempts to extract a payload from the public key passed to it during authentication.

Command and Control

1 technique
T1219Remote Access ToolsEvidence1

The resulting malicious build interferes with authentication in sshd via systemd... Under the right circumstances this interference could potentially enable a malicious actor to break sshd authentication and gain unauthorized access to the entire system remotely.

Activity feed

Recent activity

5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
malware newsNews · Oct 19, 2026What Is a Backdoor? Meaning, Types, Real Examples, Detection & Removal (2026 Guide) - Malware News - Malware Analysis, News and IndicatorsSupply-chain backdoor inserted through obfuscated build files into XZ Utils releases. It was designed to bypass SSH authentication on affected Linux systems and was discovered after unexpected SSH login delays prompted investigation.Read more ↗riskyNews · Jul 20, 2026Risky Bulletin: Hacker wipes Romania's entire land registry database - Risky Business MediaA backdoor introduced into XZ Utils in the 2024 incident. This reference mentions a retrospective account without describing its technical capabilities.Read more ↗falconfeeds blogNews · Feb 27, 2025The Politics of Patch Delays: When Vulnerability Disclosure Collides with National InterestsMalicious code planted in XZ Utils after a contributor using the persona Jia Tan gained maintainer access through years of trust-building. According to the content, the backdoor targeted OpenSSH to enable remote execution. Suggested state attribution remains speculative.Read more ↗ncsc nl newsNews · May 22, 2024De XZ-factor: sociale kwetsbaarheden in open source projecten | NCSCA malicious, obfuscated supply-chain backdoor inserted into XZ Utils/liblzma build-related code. When incorporated into affected Linux distribution builds, it added checks to SSH-related connection handling and could grant system-level SSH access to an operator using a specific cryptographic key.Read more ↗
+1 more in the timeline. Sign up to see them
Is this in your environment?See whether this family's indicators match your telemetry and which of your assets are exposed to the CVEs associated with it.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets match these IOCs, which detections are missing, which campaigns to expect next, and what to do in the next 30 minutes.
IOC matchingMatch every observed IP, domain, and hash against your live telemetry.
Associated threat actors1Groups linked to this family, with evidence pinned to each claim.
Associated vulnerabilities1CVEs linked to this family, with the reporting behind each link.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
MITRE ATT&CK mapping9Every documented technique, ranked by evidence weight.
Researcher chatterReddit, Mastodon, and CTI community discussion around this family.