Which versions of neov are malicious?

The following PyPI versions of neov are flagged malicious: 0.1.0, 0.2.0. Treat any of these as compromised.

How do I remediate neov if I installed it?

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

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

Yes — neov is associated with the 2025-04-qtpv 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 neov across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for neov (2 malicious versions).

Malicious package

neovPyPI

Advisory published Apr 25, 2025Updated Dec 12, 2025

neov is a confirmed malicious PyPI package (MAL-2025-191801) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in neov (PyPI)

MAL-2025-191801

Immediate action

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

pip uninstall neov

What this malware does

Importing the module starts exfiltration of ".session" files, which appear to be used at least by one Telegram library (https://docs.telethon.dev/en/stable/concepts/sessions.html#what-are-sessions) to store credentials

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

Campaign: 2025-04-qtpv

Reasons (based on the campaign):

files-exfiltration
target:telegram

Malicious versions

2 flagged

0.1.00.2.0

Indicators of compromise (SHA-256)

a0229deb84cc85e99c1216b08fcd5f37a378163daef1907151cab4b6cb6838a5

0c9e3f275318dc63c36dbc902dfd73c0b3aa4fa830d114c0833ed8d24258d9b0

16843f3c0cc2cf743b60dab65be25efc809a21f4e09d709479ca647ff7cc8c8d

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for neov (2 malicious versions).
If you installed it — respond
neov 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 neov 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. neov on PyPI has been identified as a malicious package (versions 0.1.0, 0.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-04-qtpv

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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