Which versions of nai are malicious?

The following PyPI versions of nai are flagged malicious: 1.4, 1.5, 1.6, 1.7, 1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.8, 2.9, 3.0, 3.1. Treat any of these as compromised.

How do I remediate nai if I installed it?

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

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

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

Search your lockfiles and build artifacts for nai (16 malicious versions).

Malicious package

naiPyPI

Advisory published Mar 13, 2026Updated Mar 13, 2026

nai is a confirmed malicious PyPI package (MAL-2026-1408) that steals credentials and exfiltrates sensitive data (malicious versions 1.4, 1.5, 1.6…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nai (PyPI)

MAL-2026-1408

Immediate action

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

pip uninstall nai

What this malware does

Package is a hacking tool that not only abuses 3rd-party services but also silently exfiltrates credentials the user uses to log in there. The provided account is also forced to follow the attacker's accounts.

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

Campaign: 2026-03-old-nai

Reasons (based on the campaign):

exfiltration-credentials
abusing-3rd-api
action-hidden-in-lib-usage

Malicious versions

16 flagged

1.41.51.61.71.81.92.02.12.22.32.42.52.82.93.03.1

Indicators of compromise (SHA-256)

a9e4650a322afd07ff77c3f934248e52f477f2d1cebd0c84b1074bdba1142efe

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for nai (16 malicious versions).
If you installed it — respond
nai 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 nai 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. nai on PyPI has been identified as a malicious package (versions 1.4, 1.5, 1.6, 1.7, 1.8, 1.9, 2.0, 2.1, and 8 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-03-old-nai

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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