Which versions of pingdomv3 are malicious?

The following PyPI versions of pingdomv3 are flagged malicious: 0.0.2, 0.0.3, 0.0.4, 0.0.6, 0.1, 0.1.1, 1.0.0, 1.1.0. Treat any of these as compromised.

How do I remediate pingdomv3 if I installed it?

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

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

Yes — pingdomv3 is associated with the RLMA-2024-04261, RLUA-2024-08689, RLUA-2025-01228, 2024-04-pingdomv3, RLUA-2026-00592 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 pingdomv3 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pingdomv3 (8 malicious versions).

Malicious package

pingdomv3PyPI

Advisory published Jun 25, 2024Updated Mar 19, 2026

pingdomv3 is a confirmed malicious PyPI package (MAL-2024-5479) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.2, 0.0.3, 0.0.4…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pingdomv3 (PyPI)

MAL-2024-5479

Immediate action

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

pip uninstall pingdomv3

What this malware does

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

Campaign: 2024-04-pingdomv3

Reasons (based on the campaign):

reuse-removed-name
obfuscation

Malicious versions

8 flagged

0.0.20.0.30.0.40.0.60.10.1.11.0.01.1.0

Indicators of compromise (SHA-256)

00a5e2b57cf2513835ea68649af9099898c7e87d1e32448997846996e816f2b9

8fc8e0ff2c04e8849ea90181be10fb4f16725ed4a426359534711dd0802a2518

6dab266679decc6fb9cd654cccb5f12921c97012dac79703d0ed3859055279de

c5501b0e8e29fc5a8adb5676e0914d0fbb910f8ccc5faf0aad13d2dee2d7a87d

7b1fe453efd67c0475761e84e07029086b389cedfb367f38826c0d3339b62b01

ef6d3ae3ce0d5313f14763990d06cdd34211a6d1abf80496dee226769eb2ddf2

26deafd6bb1c610ab0d6bff25c2d64988f186d59f53351b3b94184f5fe15fffe

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for pingdomv3 (8 malicious versions).
If you installed it — respond
pingdomv3 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 pingdomv3 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. pingdomv3 on PyPI has been identified as a malicious package (versions 0.0.2, 0.0.3, 0.0.4, 0.0.6, 0.1, 0.1.1, 1.0.0, 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-04261RLUA-2024-08689RLUA-2025-012282024-04-pingdomv3RLUA-2026-00592

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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