Which versions of hellopythopyy are malicious?

The following PyPI versions of hellopythopyy are flagged malicious: 0.19.0, 0.21.0, 0.23.0, 0.24.0, 0.29.0. Treat any of these as compromised.

How do I remediate hellopythopyy if I installed it?

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

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

Yes — hellopythopyy is associated with the RLMA-2024-11060, GENERIC-simple-tests, RLUA-2026-00385 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 hellopythopyy 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 hellopythopyy (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hellopythopyy across your stack and pipelines.

Malicious package

hellopythopyyPyPI

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

MAL-2024-11607

Immediate action

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

pip uninstall hellopythopyy

What this malware does

Packages that might be part of testing for pentesting / malicious activity / joy, with suspicious activity that does not present any real harm.

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: GENERIC-simple-tests

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

5 flagged

0.19.00.21.00.23.00.24.00.29.0

Indicators of compromise (SHA-256)

f169a1d53d6f48158da348ce6932c104e354040b1d9c68b54a13e959dbe98e29

61945852a5082bbf26645b011ba17e53feb970d0ef0c3b2ee26bad6c4e535d94

4d534cccb22ee1d1a160d632f8698201e94ea1c69129838084362bd42c52a9a9

6e3cef62bb079447045a1bfaec523255ebeaf10db7c1def025032e4527a58fa3

c09104ed0575e9b28c75f2495025cccff0ecc2ef295e3206f573802e62400ecb

6c16f3be9a91335a3969e91be596931a3ffaba239bdde233e870eaf15bbbf5f6

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

Campaign

RLMA-2024-11060GENERIC-simple-testsRLUA-2026-00385

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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