Which versions of someeebbb are malicious?

The following PyPI versions of someeebbb are flagged malicious: 10.0.5. Treat any of these as compromised.

How do I remediate someeebbb if I installed it?

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

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

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

Malicious package

someeebbbPyPI

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

MAL-2025-41764

Immediate action

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

pip uninstall someeebbb

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

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-standard-pypi-install-pentest

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.

Malicious versions

1 flagged

10.0.5

Indicators of compromise (SHA-256)

38b819f00b8e362e65add39defd3562a3215a422770ef9716e3bfcd9e9d98a30

bd32e89204a063b5760ff18b4955ef3c66c070595e91b5f19b9d0d816bf1f354

0fd59432f228380b77cbfb70e5a776f13b909d7be4b57ce72e270f41ac035ee0

f4a4cbaee28c6326126d8dec4a74dedf3cf8f59e0631aeea5696c037b1bf9f0b

4b620243b7a42fbad3d0c66301a1ae7d3ad358d157429725fda8ab161bdc7547

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

Campaign

RLMA-2025-04262GENERIC-standard-pypi-install-pentestRLUA-2026-00773

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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