Which versions of nvtorch-oot-nightly are malicious?

The following PyPI versions of nvtorch-oot-nightly are flagged malicious: 99999.0.0, 99999.0.1. Treat any of these as compromised.

How do I remediate nvtorch-oot-nightly if I installed it?

nvtorch-oot-nightly 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 nvtorch-oot-nightly — how do I know if it already compromised me?

If nvtorch-oot-nightly 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.

Is nvtorch-oot-nightly part of a known attack campaign?

Yes — nvtorch-oot-nightly is associated with the GENERIC-standard-pypi-install-pentest, IN-MAL-2026-011258, IN-MAL-2026-011239 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 nvtorch-oot-nightly across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for nvtorch-oot-nightly (2 malicious versions).

Malicious package

nvtorch-oot-nightlyPyPI

Advisory published Aug 1, 2026Updated Aug 4, 2026

nvtorch-oot-nightly is a confirmed malicious PyPI package (MAL-2026-11425) that steals credentials and exfiltrates sensitive data (malicious versions 99999.0.0, 99999.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nvtorch-oot-nightly (PyPI)

MAL-2026-11425

Immediate action

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

pip uninstall nvtorch-oot-nightly

What this malware does

The package's setup.py issues an install-time HTTP request to the hardcoded bare-IP URL http://167.233.212.138/cb/db27bcff144c059f/nvtorch_oot_nightly using urlopen with a 5-second timeout. The request fires automatically on pip install, notifying the operator of the remote endpoint that the package was installed and leaking the installer's source IP and network metadata over plain HTTP. The package name (nvtorch-oot-nightly) and version (99999.0.1) shadow a plausible internal NVIDIA/PyTorch namespace with a high version to win resolution against an internal index — the canonical dependency-confusion shape. The path component cb/db27bcff144c059f/nvtorch_oot_nightly encodes a per-target identifier used to correlate installs back to the specific victim organization.

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

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: GENERIC-standard-pypi-install-pentest

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.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

2 flagged

99999.0.099999.0.1

Indicators of compromise (SHA-256)

0f81b904b849df393cbe5c34f952af65d8b28e0797e33d62cf964df77d4929c7

64d0b909171c36fd0e36f975f61e1cd64fe90036b669987ba5b64393d72bda10

d92503f2178663997d57ffa45fbb89f4a55de70e94f66745b4edf283a98e830f

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for nvtorch-oot-nightly (2 malicious versions).
If you installed it — respond
nvtorch-oot-nightly 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 nvtorch-oot-nightly 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

No. nvtorch-oot-nightly on PyPI has been identified as a malicious package (versions 99999.0.0, 99999.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-standard-pypi-install-pentestIN-MAL-2026-011258IN-MAL-2026-011239

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks nvtorch-oot-nightly-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

Explore

All malware advisories How O3 detects malware Vulnerability database