lightningPyPI
Advisory published Updated
lightning is a confirmed malicious PyPI package (MAL-2026-3201) that steals credentials and exfiltrates sensitive data (malicious versions 2.6.2, 2.6.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in lightning (PyPI)
What this malware does
Versions 2.6.2, 2.6.3 were compromised.
Compromised versions contain injected code that starts automatically during importing the module, downloads (legitimate) JavaScript runtime, and executes included JavaScript infostealer. It collects credentials from multiple sources (e.g. files, process memory, cloud metadata endpoints, CLI commands like gh or gcloud), sensitive cryptocurrency data, shell history files. It also attempts to spread itself using discovered credentials to other repositories and packages.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-04-compr-lightning
Reasons (based on the campaign):
-
infostealer
-
files-exfiltration
-
exfiltration-ssh-keys
-
exfiltration-crypto
-
exfiltration-credentials
-
compromised-package
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for lightning (2 malicious versions).
If you installed it — respond
lightning is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If lightning was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Kamil Mańkowski (kam193) · analyst
Detect & block this
O3 blocks lightning-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.