Which versions of pplgdfhuighsdfyisfgfd are malicious?

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

How do I remediate pplgdfhuighsdfyisfgfd if I installed it?

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

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

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

Malicious package

pplgdfhuighsdfyisfgfdPyPI

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

MAL-2024-11663

Immediate action

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

pip uninstall pplgdfhuighsdfyisfgfd

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)

72dda5da73096649c5d5ec87461b4647f5ca7865a79f0f52c09400a68d31be1a

0bdb765bf7484f8e56e73e5fb2bca2a9edb90de38d7fd7b575784707350880c1

1b4e49a8011af86af7ac1b8cf4760295ddcf33d4b354139db3d92192e813dcc9

5eb55bcd9d0a1f9014156c54f8ebb2ca1806fc560d822f93ce95d8929f91b7b4

d077d9fc7b36f007e350bf7c058470c090f1e505722852623e56410f41ee28c8

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

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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