Which versions of hellopythopy are malicious?

The following PyPI versions of hellopythopy are flagged malicious: 0.1.0, 0.2.0, 0.3.0, 0.4.0, 0.5.0, 0.8.0, 0.9.0, 0.11.0, 0.14.0, 0.16.0, 0.19.0. Treat any of these as compromised.

How do I remediate hellopythopy if I installed it?

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

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

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

Malicious package

hellopythopyPyPI

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

MAL-2024-11606

Immediate action

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

pip uninstall hellopythopy

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

11 flagged

0.1.00.2.00.3.00.4.00.5.00.8.00.9.00.11.00.14.00.16.00.19.0

Indicators of compromise (SHA-256)

43a94bfed11f79dfd78243d3200802c7d00c2d57970eacab989606f0bb179e1e

07f1712190e0f9bc1ff94a4ec5e864dfa8cb65a3f2560019a11966ccf75fd71d

9d4a25ed4b69dc1e63e0582d7ec37abf5fb0e5adb1e844dda88557faa06bd827

3181f7e5aa889d0eea9caf2cea9d0be52c829f676de99bd493f11922898c51b3

05a04c7f2cc96be81294da55c77d5758321ab422632c437b7b670b0c572eab06

966436b19d9e584ef16ad6ff04db34f1d580a44fc5652ca08818dd7a9fc30e10

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 hellopythopy (11 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hellopythopy across your stack and pipelines.
If you installed it — respond
Remove hellopythopy 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 hellopythopy 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 hellopythopy 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. hellopythopy on PyPI has been identified as a malicious package (versions 0.1.0, 0.2.0, 0.3.0, 0.4.0, 0.5.0, 0.8.0, 0.9.0, 0.11.0, and 3 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-11059GENERIC-simple-testsRLUA-2026-00384

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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