Which versions of hellohackers are malicious?

The following PyPI versions of hellohackers are flagged malicious: 0.0.0. Treat any of these as compromised.

How do I remediate hellohackers if I installed it?

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

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

Yes — hellohackers is associated with the RLMA-2025-01218, 2025-02-hellohackers, RLUA-2026-00382 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 hellohackers 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 hellohackers (version 0.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hellohackers across your stack and pipelines.

Malicious package

hellohackersPyPI

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

MAL-2025-1977

Immediate action

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

pip uninstall hellohackers

What this malware does

File contains a metapreter beacon that runs in the setup.py. Analysed version uses a local IP as the target.

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

Campaign: 2025-02-hellohackers

Reasons (based on the campaign):

The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.

Malicious versions

1 flagged

0.0.0

Indicators of compromise (SHA-256)

c2de01c21a8aa72a0ad26f9f27c1f3897622d0264fd4017c067256ce42d533af

9e3856f0b40aa18b9020c86248b2322cdcccf971a35bcf2f502cf25d2d38720b

63788f1f3223270be7955b619eb09fa7e7f401084e4332ed732d33b522782a37

d39a526ef9f55702e95ae7871404e884b47fe089c1d11a5aa131114a756435be

aa2161662c602b5ffae5248792acb5bab83240fd1faf38ac3b270fbedb2352ca

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

Campaign

RLMA-2025-012182025-02-hellohackersRLUA-2026-00382

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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