Which versions of ggghhhrrr are malicious?

The following PyPI versions of ggghhhrrr are flagged malicious: 0.1, 0.3. Treat any of these as compromised.

How do I remediate ggghhhrrr if I installed it?

Remove ggghhhrrr from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed ggghhhrrr — how do I know if it already compromised me?

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

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

Malicious package

ggghhhrrrPyPI

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

MAL-2024-11600

Immediate action

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

pip uninstall ggghhhrrr

What this malware does

According to the description, packages should demonstrate the dependency confusion attack. The realisation is, in fact, a spamming with packages having as the only purpose reporting basic data like hostname and current working directory.

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-lokopoil23

Reasons (based on the campaign):

dependency-confusion

Malicious versions

2 flagged

0.10.3

Indicators of compromise (SHA-256)

170b2ff6390bb577a4ac72da172794ab959b9f0863babf17a50e11b4d7530950

b50ce7dd2c9d615def1bd7c9c70ba56aa6fab4d943aba1b54eca90d5aeb1bffa

28a551f5605f075f623a22621731c74e18e92b9e3eafef6d876457301fbeee20

be72f9c384b25f5a4090053d73874fe323167b6954c3a6a16b16b8335a946999

80cf2b6d54b18cacb40847c80d5a3049a8915374cc4e4e61262022f9187dab08

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ggghhhrrr (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ggghhhrrr across your stack and pipelines.
If you installed it — respond
Remove ggghhhrrr from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If ggghhhrrr 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 ggghhhrrr 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. ggghhhrrr on PyPI has been identified as a malicious package (versions 0.1, 0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-110522024-10-lokopoil23RLUA-2026-00351

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks ggghhhrrr-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring