PyTorch Lightning Compromised in PyPI Supply Chain Attack to Steal Credentials
Overview
PyTorch Lightning, a widely used Python package, has been compromised in a supply chain attack, with attackers pushing two malicious versions—2.6.2 and 2.6.3—on April 30, 2026. This incident, identified by cybersecurity firms Aikido Security, Socket, and StepSecurity, aims to steal user credentials. Developers and organizations that use these specific versions are at risk, as the malicious code can capture sensitive information. Users are urged to quickly check their installations and update to secure versions to avoid potential credential theft. This attack emphasizes ongoing vulnerabilities within software supply chains, highlighting the need for vigilance among developers and users alike.
Key Takeaways
- Active Exploitation: This vulnerability is being actively exploited by attackers. Immediate action is recommended.
- Affected Systems: PyTorch Lightning versions 2.6.2 and 2.6.3
- Action Required: Users should update to a secure version of PyTorch Lightning immediately.
- Timeline: Disclosed on April 30, 2026
Original Article Summary
In yet another software supply chain attack, threat actors have managed to compromise the popular Python package Lightning to push two malicious versions to conduct credential theft. According to Aikido Security, Socket, and StepSecurity, the two malicious versions are versions 2.6.2 and 2.6.3, both of which were published on April 30, 2026. The campaign is assessed to be an extension of the
Impact
PyTorch Lightning versions 2.6.2 and 2.6.3
Exploitation Status
This vulnerability is confirmed to be actively exploited by attackers in real-world attacks. Organizations should prioritize patching or implementing workarounds immediately.
Timeline
Disclosed on April 30, 2026
Remediation
Users should update to a secure version of PyTorch Lightning immediately.
Additional Information
This threat intelligence is aggregated from trusted cybersecurity sources. For the most up-to-date information, technical details, and official vendor guidance, please refer to the original article linked below.
Related Topics: This incident relates to Update.