tpu-raiden-jaxPyPI
Advisory published Updated
tpu-raiden-jax is a confirmed malicious PyPI package (MAL-2026-15930) that steals credentials and exfiltrates sensitive data (malicious version 99.99.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tpu-raiden-jax (PyPI)
What this malware does
On first import, tpu-raiden-jax's top-level init.py invokes a canary() routine that serializes the entire os.environ dictionary along with socket.gethostname() and POSTs the resulting JSON payload to the hardcoded URL https://vuorblucjega.dssldrf.net/python-install-log/tpu-raiden-jax via urllib.request. Errors are silently swallowed. The destination host is unrelated to any legitimate publisher domain, and the package version (99.99.0) plus the bulk-environment shape are consistent with a dependency-confusion canary/steal against internal package names. Any secrets present in the environment of a REPL, CI job, or build that imports this package (AWS*, GH_TOKEN, npm/PyPI tokens, database credentials, and any other exported variable) are transmitted to the external host.
During import, the package exfiltrates environment variables.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-09-amirgo4496
Reasons (based on the campaign):
-
exfiltration-env-variables
-
dependency-confusion
-
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for tpu-raiden-jax (version 99.99.0).
If you installed it — respond
tpu-raiden-jax 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 tpu-raiden-jax 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
- Amazon Inspector · finder
- Kamil Mańkowski (kam193) · reporter
Detect & block this
O3 blocks tpu-raiden-jax-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.