Which versions of pplgdfhuighsdfyisfdty are malicious?

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

How do I remediate pplgdfhuighsdfyisfdty if I installed it?

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

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

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

Malicious package

pplgdfhuighsdfyisfdtyPyPI

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

MAL-2024-11661

Immediate action

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

pip uninstall pplgdfhuighsdfyisfdty

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)

184915326647ad3b19088447e38959cbbc246318d52670da620086f3c2474b23

aaadf7c5d9b51f1e1471ff375bcbfeb88c72f46378dcf1fbf33e85f23bd04c6c

a6da12f1a169dc997d18e49311bb47be99e753dca10106e2bde591c0618268d1

0b41dcca8bb627a4f5bcc696eed782110f13efe482c7f6d793626cd23ae9d481

7b6a99d0fe2a6d92b00d6aa2acfe2dbb2df2c9f24e1a7fea18a15abf4fcc2a49

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 pplgdfhuighsdfyisfdty (version 1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pplgdfhuighsdfyisfdty across your stack and pipelines.
If you installed it — respond
pplgdfhuighsdfyisfdty 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 pplgdfhuighsdfyisfdty 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 pplgdfhuighsdfyisfdty 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. pplgdfhuighsdfyisfdty 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-111182024-10-gal32fjdsbf89hnd-gcp-tokenRLUA-2026-00601

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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