What does the whel malware do?

Package uses the template from https://github.com/thegoodhackertv/malpip to explore building malicious PyPI packages. Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: SCRIPT_KIDDIE-thegoodhacker-paquete Reasons (based on the campaign): - The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk. - The package overrides the install command in setup.py to execute malicious code during installation. - Package uses simple pre-prepared tools to create a low-quality malicious action.

Which versions of whel are malicious?

The following PyPI versions of whel are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate whel if I installed it?

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

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

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

Malicious package

whelPyPI

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

MAL-2025-5144

Immediate action

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

pip uninstall whel

What this malware does

Package uses the template from https://github.com/thegoodhackertv/malpip to explore building malicious PyPI packages.

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

Campaign: SCRIPT_KIDDIE-thegoodhacker-paquete

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.
Package uses simple pre-prepared tools to create a low-quality malicious action.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

8b42afd43b449679bed7257f7c58d910c76359f62080ac8ed0ad85bb59ca80f9

b29ba207483b2c8c39557a7ba728abfa5c536086a9a42e19f60d14c30ed96658

556e14c71baa5758239b80d9333f83a0369b1169e63b027c50d633b97475136c

14900319e04f7c35cf2ef793c8f23a53c4bd95642165138b7664eac80531b193

946d71d17feba0d99649f12daa651b532e84374534433f5080519087701f8b20

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

Campaign

RLMA-2025-03041SCRIPT_KIDDIE-thegoodhacker-paqueteRLUA-2026-00929

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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