Which versions of nuest are malicious?

The following PyPI versions of nuest are flagged malicious: 99.7. Treat any of these as compromised.

How do I remediate nuest if I installed it?

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

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

Yes — nuest is associated with the 2024-11-byted-dast 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 nuest across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for nuest (version 99.7).

Part of a larger attack: 2024-11-byted-dast published 183 malicious packages. See the full campaign →

Malicious package

nuestPyPI

Advisory published Nov 5, 2024Updated Dec 12, 2025

nuest is a confirmed malicious PyPI package (MAL-2024-10372) that steals credentials and exfiltrates sensitive data (malicious version 99.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nuest (PyPI)

MAL-2024-10372

Immediate action

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

pip uninstall nuest

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-11-byted-dast

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
typosquatting
dependency-confusion

The OpenSSF Package Analysis project identified 'nuest' @ 99.7 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.7

Indicators of compromise (SHA-256)

ee9de982f050cb2906cb58f9a7e13c20af350d093f901061240af152f27edd8d

641c66342cb972e320b60d3a7ed161f28d7e06faee435b1c30c4558898f92552

b492bc7bd440cf222a12c711590d7035a901a290bea145c0df822b55e57c0ebb

85e15976cd5c53ba0d3085f892dbaec0488cb9f04a14056b293e36065a4cdf43

Detection & response playbook

Credential / info stealer

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

Campaign

2024-11-byted-dast

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder

Detect & block this

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