Which versions of whalebone7-poc are malicious?

The following PyPI versions of whalebone7-poc are flagged malicious: 0.0.4. Treat any of these as compromised.

How do I remediate whalebone7-poc if I installed it?

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

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

Yes — whalebone7-poc is associated with the RLMA-2025-02017, GENERIC-questionable-pentest, RLUA-2026-00927 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 whalebone7-poc 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 whalebone7-poc (version 0.0.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging whalebone7-poc across your stack and pipelines.

Malicious package

whalebone7-pocPyPI

Malicious code in whalebone7-poc (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-3018

Immediate action

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

pip uninstall whalebone7-poc

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.0.4

Indicators of compromise (SHA-256)

978ae30dd556467c7d85643cafb7a1387c25cb36722109096883c8f10bc11329

c3d4c5b0f832fd1a0c08f365fd1d025713609fd8b3b19f76c73f16ceae4b5a14

ebd207a56329855d7d146895e375b39fcbe907f6ff2e7489a80bbe7c6d4a01fc

42e3fe3802f956064dbfe5cf986e0b22a8d0637abf9c7e1441c6a16c8a5840ca

3229ec52e62244118ff2b839c6132a3d74a206bdcaeb54a0ed3fe56533409aa7

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

Campaign

RLMA-2025-02017GENERIC-questionable-pentestRLUA-2026-00927

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks whalebone7-poc-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