Which versions of pplgdfhuighsdfyisfdty2 are malicious?

The following PyPI versions of pplgdfhuighsdfyisfdty2 are flagged malicious: 1. Treat any of these as compromised.

How do I remediate pplgdfhuighsdfyisfdty2 if I installed it?

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

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

Yes — pplgdfhuighsdfyisfdty2 is associated with the RLMA-2024-11119, 2024-10-gal32fjdsbf89hnd-gcp-token, RLUA-2026-00602 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 pplgdfhuighsdfyisfdty2 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 pplgdfhuighsdfyisfdty2 (version 1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pplgdfhuighsdfyisfdty2 across your stack and pipelines.

Malicious package

pplgdfhuighsdfyisfdty2PyPI

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

MAL-2024-11662

Immediate action

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

pip uninstall pplgdfhuighsdfyisfdty2

What this malware does

Installing the package attempts to exfiltrate GCP tokens. As it uses a random names and/or targets specific accounts, it's most probably a (pen)test.

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: 2024-10-gal32fjdsbf89hnd-gcp-token

Reasons (based on the campaign):

exfiltration-cloud-tokens

Malicious versions

1 flagged

Indicators of compromise (SHA-256)

c719a8a872cfb7df01603203cfaeb05185ac23e5cef95a2c10f0a8eadeb10e61

141e88965d0e02ed4914bcb22b82b7c2a511a5676c676f4a17ee6e5950819adb

b38f6d0da39d944ddde3bda8742a42099398148ad778fb06fe57e6a3274ea2e8

fbc4900c2ef9c384623b840be0a2a3fb2520d61d8b4660ebdbe4c922df593692

d331657a9e2612427ff593548458531d24ce748f89912e0e9ccf5cc580724c1a

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 pplgdfhuighsdfyisfdty2 (version 1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pplgdfhuighsdfyisfdty2 across your stack and pipelines.
If you installed it — respond
pplgdfhuighsdfyisfdty2 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 pplgdfhuighsdfyisfdty2 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 pplgdfhuighsdfyisfdty2 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. pplgdfhuighsdfyisfdty2 on PyPI has been identified as a malicious package (version 1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-111192024-10-gal32fjdsbf89hnd-gcp-tokenRLUA-2026-00602

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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