Which versions of numprint are malicious?

The following PyPI versions of numprint are flagged malicious: 1.2.0. Treat any of these as compromised.

How do I remediate numprint if I installed it?

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

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

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

Search your lockfiles and build artifacts for numprint (version 1.2.0).

Malicious package

numprintPyPI

Advisory published Oct 27, 2026Updated Oct 27, 2026

numprint is a confirmed malicious PyPI package (MAL-2026-18343) that steals credentials and exfiltrates sensitive data (malicious version 1.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in numprint (PyPI)

MAL-2026-18343

Immediate action

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

pip uninstall numprint

What this malware does

During installation the package starts a background process executing commands provided by the attacker. The C2 communication happens through a GitHub Gist.

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

Campaign: 2026-10-numprint

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.
rat

Malicious versions

1 flagged

1.2.0

Indicators of compromise (SHA-256)

ca6ff316077349c92e2d1e5d7c3683a16e6542b952d5c7fc8743efa5d4c80243

Detection & response playbook

Credential / info stealer

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

Campaign

2026-10-numprint

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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