Which versions of hello-world-package-test are malicious?

The following PyPI versions of hello-world-package-test are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate hello-world-package-test if I installed it?

hello-world-package-test 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 hello-world-package-test — how do I know if it already compromised me?

If hello-world-package-test 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 hello-world-package-test part of a known attack campaign?

Yes — hello-world-package-test is associated with the RLMA-2024-08342, GENERIC-questionable-pentest, RLUA-2026-00381 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 hello-world-package-test 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 hello-world-package-test (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hello-world-package-test across your stack and pipelines.

Malicious package

hello-world-package-testPyPI

Malicious code in hello-world-package-test (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-10034

Immediate action

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

pip uninstall hello-world-package-test

What this malware does

Generic campaign for all (likely) research / pentests, where the amount or art of collected data raises questions about the privacy, security and ethical side.

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

Campaign: GENERIC-questionable-pentest

Reasons (based on the campaign):

exfiltration-env-variables
exfiltration-generic
The package overrides the install command in setup.py to execute malicious code during installation.
typosquatting

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

8834c383b898763df77528490f8fde69de2d37271a28963d4a36b8a2dec2169a

6ec758ec3e5857bd09d1962efe779fe1970d838a21ee03a1c2a51854c7aa595d

8ee148c559a9993ef0660c9183434ff59d2f6430a126a5913ef9a8341b9014ff

1ec67dd8dc68984872516a4e3db57466c58af4c282ddeaf8f32615221944471f

c1ae4dd2bbda1a2a5e1db5dc14aa5580c2bf6f41ac5539736273bec7dbd1af70

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

Campaign

RLMA-2024-08342GENERIC-questionable-pentestRLUA-2026-00381

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks hello-world-package-test-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