Which versions of nump are malicious?

The following PyPI versions of nump are flagged malicious: 1, 1.3.3.7, 3.3.0.1, 5.5.5.5. Treat any of these as compromised.

How do I remediate nump if I installed it?

nump is a typosquat — you almost certainly intended a legitimately-named package. Remove nump, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed nump — how do I know if it already compromised me?

If nump was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is nump part of a known attack campaign?

Yes — nump is associated with the GENERIC-local-typosquatting 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 nump across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nump (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nump across your stack and pipelines.

Malicious package

numpPyPI

Malicious code in nump (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-2013

Immediate action

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

pip uninstall nump

What this malware does

Package is a typosquatting or dependency confusion attempt with a low-harm local-only action, like leaving a flag file.

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: GENERIC-local-typosquatting

Reasons (based on the campaign):

dependency-confusion
The package overrides the install command in setup.py to execute malicious code during installation.
typosquatting

Malicious versions

4 flagged

11.3.3.73.3.0.15.5.5.5

Indicators of compromise (SHA-256)

daf533091c2cd6d2ae82e47f2ba9264b23395105f9c088018560c13cea33801f

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nump (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nump across your stack and pipelines.
If you installed it — respond
nump is a typosquat — you almost certainly intended a legitimately-named package. Remove nump, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If nump was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks nump before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. nump on PyPI has been identified as a malicious package (versions 1, 1.3.3.7, 3.3.0.1, 5.5.5.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-local-typosquatting

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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