Loading story…
A severe flaw in PuTTY and several applications that reuse its code can expose private keys used with the NIST P-521 ECDSA algorithm. The weakness causes the software to generate insufficiently random nonces, allowing an attacker to recover a victim’s private key after collecting roughly 60 signatures from the vulnerable implementation. The issue affects PuTTY as well as tools including FileZilla, WinSCP, and TortoiseGit; users of TortoiseSVN were advised to replace Plink with the latest PuTTY version until an official fix becomes available. Organizations were urged to update immediately and treat any affected P-521 key pairs as potentially compromised because recovered keys could be reused for SSH authentication or other trusted public-key access.
Separately, a critical compromise in XZ Utils introduced malicious code into versions 5.6.0 and 5.6.1, creating a supply-chain backdoor that could enable unauthorized access on affected Linux systems, with SSH identified as a primary exposure path. Defenders were advised to downgrade to version 5.4.6 immediately, consider disabling SSH if rollback was not possible, and verify system integrity because patching alone may not be enough if the backdoor was already exploited. The alerts noted that some Linux distributions had shipped the tainted versions while others were not observed to be vulnerable or had already issued updates.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
4 events from the most recent confirmed update back to the earliest known activity.
Fixed versions became available for PuTTY, FileZilla, WinSCP, and TortoiseGit following disclosure of the ECDSA flaw, while TortoiseSVN users were advised to replace Plink with the latest PuTTY version until an official fix is released.
A serious vulnerability was disclosed in PuTTY's implementation of the NIST P-521 ECDSA algorithm, where weak nonce generation could allow an attacker to recover a private key after collecting about 60 signatures from the vulnerable implementation.
Guidance was issued to immediately downgrade XZ Utils to version 5.4.6 or disable SSH if rollback was not possible, with some Linux distributions already releasing updates while users were warned to verify system integrity in case exploitation had occurred.
A critical supply-chain compromise was identified in XZ Utils versions 5.6.0 and 5.6.1, where malicious code introduced a backdoor that could enable unauthorized access, particularly via SSH on affected Linux systems.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
2 references tracked. Mallory keeps watching after this page renders.
kyberturvallisuuskeskus.fi
Open sourcekyberturvallisuuskeskus.fi
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
A critical flaw in **PuTTY** tracked as **`CVE-2024-31497`** allowed recovery of **NIST P-521 ECDSA private keys** because the client generated biased nonces during signature creation. Public advisories and downstream vendor notices said the issue affected PuTTY-based signing operations and could let attackers derive a private key from a sufficient number of signatures, putting SSH authentication and related trust relationships at risk where vulnerable keys were used. The vulnerability was disclosed through **oss-security** and subsequently addressed by multiple Linux vendors, including **Red Hat**, **SUSE**, and **Debian LTS**, while **Citrix** warned administrators to apply manual mitigations for affected environments. The broad guidance across advisories was to **upgrade PuTTY to a fixed release**, stop using impacted **P-521** keys for signing, and **rotate any potentially exposed private keys** and dependent authorized keys or certificates to prevent continued compromise.
Jul 12, 2026
A malicious supply-chain backdoor was discovered in **XZ Utils** versions `5.6.0` and `5.6.1`, tracked as **`CVE-2024-3094`**, after PostgreSQL developer and Microsoft engineer **Andres Freund** investigated unusual CPU behavior and traced it to `liblzma`. The tampering was hidden in release tarballs rather than plainly visible in the main Git repository, using an obfuscated **M4 macro** during the build process to generate second-stage artifacts that altered library behavior. Researchers and vendors said the poisoned build could interfere with **OpenSSH** authentication through `systemd`, creating a path for unauthorized remote access to affected Linux systems. Red Hat said **Red Hat Enterprise Linux** was not affected, but compromised packages reached **Fedora Rawhide** and **Fedora Linux 40 beta**, prompting urgent downgrade and rollback guidance to safe `5.4.x` releases; Fedora 40 reportedly did not show successful execution of the injected code. Reports also said the malicious build succeeded in **Debian unstable (Sid)**, appeared in a Debian beta branch, affected several **openSUSE** distributions, and was noted by **Kali Linux**, while stable Debian releases were not known to be impacted. The incident was widely described as a near-catastrophic attack on Linux infrastructure, with scrutiny falling on maintainer account **Jia Tan / JiaT75** and an apparent long-running social-engineering effort to gain influence over the project.
Jun 29, 2026
A malicious backdoor was discovered in **XZ Utils**, a widely used compression library, and assigned **`CVE-2024-3094`**, raising urgent concerns about software supply chain compromise across Linux environments. The tampered code was introduced into upstream release tarballs for versions **5.6.0** and **5.6.1** and could enable unauthorized remote code execution by subverting authentication workflows in systems using affected `liblzma` packages, particularly where `sshd` was linked through `systemd` integrations. Security teams were urged to identify vulnerable builds, downgrade to trusted versions, and verify package provenance across development and production systems. The incident renewed attention on the broader risk posed by foundational open-source components becoming attack vectors, echoing the long-tail impact of major infrastructure flaws such as **`CVE-2021-44228`** in **Apache Log4j**. While unrelated technically, both cases underscored how deeply embedded dependencies can create outsized enterprise exposure when compromised. Organizations were advised to strengthen software bill of materials validation, monitor upstream package integrity, and accelerate patching and rollback procedures for critical third-party libraries.
Jul 12, 2026