Which versions of seabonr are malicious?

The following PyPI versions of seabonr are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate seabonr if I installed it?

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

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

Yes — seabonr is associated with the RLMA-2024-11159, 2024-09-bondonioanderas-cryptominer, RLUA-2026-00747 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 seabonr 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 seabonr (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging seabonr across your stack and pipelines.

Malicious package

seabonrPyPI

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

MAL-2024-11701

Immediate action

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

pip uninstall seabonr

What this malware does

During installation, a cryptominer is secretly installed and started.

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

Campaign: 2024-09-bondonioanderas-cryptominer

Reasons (based on the campaign):

cryptominer
The package overrides the install command in setup.py to execute malicious code during installation.
obfuscation

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

7f5210f0d0af5501643b5ed1e2622c5ad5a4192001b7bae94fd1b95c6bfd81b4

4eb24d9c88ca861c3329c1a4ccee10533fffff47cc6da516549e92f4c5d94878

338d487f231b38056400dad7ac2135955e45c2d6c75003e23e3e08df1c69c63c

d99081b752c443f363d574a54159e2aa5ff5c7fec4be1f2ed60866ba6eb65a53

a4ab081c516874cd309bf23252e9556be81e2604c2f0407d1c4e77f85a27e42e

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 seabonr (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging seabonr across your stack and pipelines.
If you installed it — respond
seabonr 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 seabonr 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 seabonr 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. seabonr 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-111592024-09-bondonioanderas-cryptominerRLUA-2026-00747

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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