Which versions of turbod are malicious?

The following PyPI versions of turbod are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7. Treat any of these as compromised.

How do I remediate turbod if I installed it?

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

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

Yes — turbod is associated with the 2026-07-oxntime 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 turbod across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for turbod (8 malicious versions).

Malicious package

turbodPyPI

Advisory published Jul 8, 2026Updated Jul 8, 2026

turbod is a confirmed malicious PyPI package (MAL-2026-6979) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in turbod (PyPI)

MAL-2026-6979

Immediate action

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

pip uninstall turbod

What this malware does

Starting version 1.0.7, the package contains obfuscated code and embedded binary that is executed during the import, sharing many similarities with package oxntime. The embedded seems to act as a guard for further execution, with some sandbox evasion techniques and time-based actions.

Prior to 1.0.7, the package offered obfuscation techniques.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-07-oxntime

Reasons (based on the campaign):

obfuscation
The package contains code to detect if it is running in a sandbox environment.
target:android
covering-tracks

Malicious versions

8 flagged

1.0.01.0.11.0.21.0.31.0.41.0.51.0.61.0.7

Indicators of compromise (SHA-256)

78d60e25c1258021c4fb69a93456c76ef1157be852c7b9dc7165290ca599b0f7

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for turbod (8 malicious versions).
If you installed it — respond
turbod 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 turbod 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. turbod on PyPI has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-07-oxntime

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks turbod-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