Which versions of pytorch-lighting are malicious?

The following PyPI versions of pytorch-lighting are flagged malicious: 95.6. Treat any of these as compromised.

How do I remediate pytorch-lighting if I installed it?

pytorch-lighting 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.

I already installed pytorch-lighting — how do I know if it already compromised me?

If pytorch-lighting was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is pytorch-lighting part of a known attack campaign?

Yes — pytorch-lighting is associated with the 2024-11-byted-dast campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find pytorch-lighting across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pytorch-lighting (version 95.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pytorch-lighting across your stack and pipelines.

Malicious package

pytorch-lightingPyPI

Malicious code in pytorch-lighting (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-10726

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

pip uninstall pytorch-lighting

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-11-byted-dast

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
typosquatting
dependency-confusion

The OpenSSF Package Analysis project identified 'pytorch-lighting' @ 95.6 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

95.6

Indicators of compromise (SHA-256)

70f1ae5751b98883dfc590695bffd797529d562c393e6e598788afd7d5dbea7f

00e679ac7323cb66fca123ebd3fc093492d3914fcd3f52c1b31afdcc0a99f47a

62c64e574f5ad4d75ebc2c82d4cc48edb6185486f8379bfd2a7bd330ce94f50e

5d1e88540495e91df38e14492fc6f6c886971becd2bcc401527d9846fce0db32

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pytorch-lighting (version 95.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pytorch-lighting across your stack and pipelines.
If you installed it — respond
pytorch-lighting 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 pytorch-lighting was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks pytorch-lighting before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. pytorch-lighting on PyPI has been identified as a malicious package (version 95.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2024-11-byted-dast

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks pytorch-lighting-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring