nvtorch-oot-nightlyPyPI
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)
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nvtorch-oot-nightly (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nvtorch-oot-nightly across your stack and pipelines.
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 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 nvtorch-oot-nightly 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
Campaign
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.