PyTorch Lightning and Intercom-client Targeted in Supply Chain Attacks to Harvest Credentials
Malware coverage focused on infection paths, containment steps and indicators defenders should watch.
By: Artur Ślesik
Published: Apr 30, 2026
Incident status: Resolved or patched
Corroborating sources: 2
Technical review credentials: Security+ evidence | RHCSA evidence | JNCIS-SEC evidence
Trust note:This alert is maintained under HackWatch's editorial policy, with visible source records, a named responsible editor and a correction channel for disputed facts.
The published article is checked against public sources before publication, and material corrections are reflected in the article update date.
Technical reviewer note: Marcin Pocztowski reviewed this alert on Apr 30, 2026 for server impact, affected-version evidence, privilege or code-execution claims and realistic patch priority. His remediation note follows the same discipline he would use around Juniper routers and production servers: verify scope, preserve useful logs, reduce exposed management access and only then apply the fix or compensating control supported by the 2 corroborating sources.
Review our editorial policy or send corrections to [email protected].
Resolved or patched. Source coverage indicates that a fix or formal remediation has been published. Verify that updates are applied in your environment.
Two malicious versions of the PyTorch Lightning Python package, 2.6.2 and 2.6.3, were released on April 30, 2026, embedding code to steal user credentials. Security researchers quickly flagged the compromised releases, urging users to audit installed versions and rotate affected credentials to reduce exposure.
GLOBAL, April 30, 2026, 19:16 UTC
Security researchers from Aikido Security, OX Security, Socket, and StepSecurity have identified a supply chain attack involving two malicious releases of the PyTorch Lightning Python package. Versions 2.6.2 and 2.6.3, published on April 30, 2026, contained code designed to exfiltrate user credentials.
Supply chain attacks target the trust developers place in third-party software dependencies. By injecting harmful code into legitimate packages, attackers gain indirect access to numerous users and their systems.
The compromised PyTorch Lightning versions were detected soon after publication, limiting potential damage. However, the package’s widespread use in machine learning workflows raises concerns about the scale of exposure if users upgraded automatically.
The embedded malicious code aimed to harvest credentials, potentially granting attackers access to sensitive infrastructure. While full technical details remain undisclosed, the tactics align with previous Python package supply chain compromises.
In a related development, the Intercom-client package also faced similar targeting, suggesting a coordinated effort to infiltrate developer environments through trusted dependencies.
Users who installed PyTorch Lightning versions 2.6.2 or 2.6.3 should verify their installations using pip or relevant package managers. Reverting to version 2.6.1 or earlier is advised until a secure update is available.
Security experts recommend immediate rotation of all credentials linked to environments where the compromised packages were deployed. This includes API keys, cloud credentials, and internal tokens.
The incident highlights the persistent risk supply chain attacks pose to open source ecosystems. Developers and organizations are urged to strengthen defenses by implementing package integrity verification and closely monitoring dependency updates.
PyTorch Lightning maintainers have yet to release an official response but are expected to issue patched versions and guidance shortly. Security teams should stay alert to official announcements.
This attack follows a string of recent supply chain breaches affecting Python packages, underscoring the need for constant vigilance in managing third-party software.
There remains uncertainty about the full extent of the compromise. Some users may have deployed the malicious versions in production, potentially exposing sensitive data.
To mitigate future risks, organizations should adopt tools that verify package signatures and conduct behavioral analysis of dependencies before deployment.
This event reaffirms that even widely trusted open source projects can serve as entry points for sophisticated cyber threats. Robust monitoring and rapid incident response remain essential to limit impact.
Sources used for this article
The Hacker News, thehackernews.com, Multiple verified sources
