Which versions of oxntime are malicious?

The following PyPI versions of oxntime are flagged malicious: 0.0.1, 0.0.1.post1, 0.0.2, 0.0.3. Treat any of these as compromised.

How do I remediate oxntime if I installed it?

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

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

Yes — oxntime 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 oxntime across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for oxntime (4 malicious versions).

Malicious package

oxntimePyPI

Advisory published Jul 8, 2026Updated Jul 8, 2026

oxntime is a confirmed malicious PyPI package (MAL-2026-6975) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.1, 0.0.1.post1, 0.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in oxntime (PyPI)

MAL-2026-6975

Immediate action

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

pip uninstall oxntime

What this malware does

The package contains obfuscated code and embedded binary that is executed during the import. The embedded binary targets Android and seems to act as a guard for further execution, with some sandbox evasion techniques and time-based actions.

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

4 flagged

0.0.10.0.1.post10.0.20.0.3

Indicators of compromise (SHA-256)

4d96d9d5b1800042c94a33b8ac459abe42775a2c07e7cbd4ca2f689bdcf141ef

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for oxntime (4 malicious versions).
If you installed it — respond
oxntime 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 oxntime 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. oxntime on PyPI has been identified as a malicious package (versions 0.0.1, 0.0.1.post1, 0.0.2, 0.0.3 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 oxntime-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