Which versions of netping are malicious?

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

How do I remediate netping if I installed it?

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

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

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

Malicious package

netpingPyPI

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

MAL-2026-3805

Immediate action

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

pip uninstall netping

What this malware does

The package silently downloads and installs an autostart script that then monitors clipboards and replaces copied cryptowallet adresses.

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

Campaign: 2026-05-netping

Reasons (based on the campaign):

persistence
crypto-related
clipboard-modify
Downloads and executes a remote malicious script.

Malicious versions

2 flagged

0.2.01.1.0

Indicators of compromise (SHA-256)

ecc862a2bc12e6779034a99abd68c5d4ffb047f1fc2ae94407dd9e4ad54df5cf

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for netping (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging netping across your stack and pipelines.
If you installed it — respond
netping 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 netping 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 netping 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. netping on PyPI has been identified as a malicious package (versions 0.2.0, 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-05-netping

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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