Which versions of tpu-raiden-jax are malicious?

The following PyPI versions of tpu-raiden-jax are flagged malicious: 99.99.0. Treat any of these as compromised.

How do I remediate tpu-raiden-jax if I installed it?

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.

I already installed tpu-raiden-jax — how do I know if it already compromised me?

If tpu-raiden-jax 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 tpu-raiden-jax part of a known attack campaign?

Yes — tpu-raiden-jax is associated with the 2026-09-amirgo4496 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 tpu-raiden-jax 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 tpu-raiden-jax (version 99.99.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tpu-raiden-jax across your stack and pipelines.

Malicious package

tpu-raiden-jaxPyPI

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)

MAL-2026-15930

Immediate action

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

pip uninstall tpu-raiden-jax

What this malware does

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

1 flagged

99.99.0

Indicators of compromise (SHA-256)

f5e62e8c3e35de0ec83c0081e3eb91530e77815509c010b28c47de375068cd92

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 tpu-raiden-jax (version 99.99.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tpu-raiden-jax across your stack and pipelines.
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 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 tpu-raiden-jax 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. tpu-raiden-jax on PyPI has been identified as a malicious package (version 99.99.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-09-amirgo4496

References

bad-packages.kam193.eu

Credits

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database