Which versions of libtpu-nightly are malicious?

The following PyPI versions of libtpu-nightly are flagged malicious: 0.1.dev20230207. Treat any of these as compromised.

How do I remediate libtpu-nightly if I installed it?

Remove libtpu-nightly from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed libtpu-nightly — how do I know if it already compromised me?

If libtpu-nightly 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.

How do I find libtpu-nightly across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for libtpu-nightly (version 0.1.dev20230207).

Malicious package

libtpu-nightlyPyPI

libtpu-nightly is a confirmed malicious PyPI package (MAL-2023-1375) that executes malicious code on install (malicious version 0.1.dev20230207). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in libtpu-nightly (PyPI)

MAL-2023-1375

Immediate action

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

pip uninstall libtpu-nightly

What this malware does

The OpenSSF Package Analysis project identified 'libtpu-nightly' @ 0.1.dev20230207 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

0.1.dev20230207

Indicators of compromise (SHA-256)

4710fdb2d58063f6a640883c2617fc154d074a9122c261111dd2e2b10a1e9552

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for libtpu-nightly (version 0.1.dev20230207).
If you installed it — respond
Remove libtpu-nightly from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If libtpu-nightly 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. libtpu-nightly on PyPI has been identified as a malicious package (version 0.1.dev20230207 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks libtpu-nightly-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database