Which versions of roboat-additions are malicious?

The following PyPI versions of roboat-additions are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate roboat-additions if I installed it?

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

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

Yes — roboat-additions is associated with the 2026-03-roboat-addition 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 roboat-additions 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 roboat-additions (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging roboat-additions across your stack and pipelines.

Malicious package

roboat-additionsPyPI

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

MAL-2026-2280

Immediate action

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

pip uninstall roboat-additions

What this malware does

During installation package downloads and runs a malicious executable. Likely continuation of 2026-03-rowrap.

The campaign is built over a malicious Roblox API wrapper. The roboat[.]pro (later robase[.]app) domain advertises a wrapper that is either directly malicious (as roboat collected in the campaign 2026-03-rowrap) or uses a malicious dependencies (like roboat-utils). New versions are published simultaneously with malicious dependencies and quickly removed. Another advertisement channel is https://github.com/Addi9000/roboat referencing two active contributors: https://github.com/Addi9000 and https://github.com/RoCruise

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

Campaign: 2026-03-roboat-addition

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
Downloads and executes a remote executable.
The malicious code is intentionally included in a dependency of the package
malware
clones-real-package

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6e8249fcecd9e50d0a15f76664e1217784ee8a5d1412a159cc076eff2cf57a78

8821279183dbb447693e0a2a66d9b262fc34d063cd0b75158160a70131bce036

558a2961bad2da46037dab165a9187c76126fafc69b51c91b8b73a3f0a16b5a2

06d6a3471197c97a19d59f4e5e987000e3fed447ce9449325a8be19b86a1f889

650645603340ae7ece2cdd474c4358c430b96d4c3512c9b62af264b5b709200f

70dd8f359a78dc1edd3a6f49bb17667a5614f46df7a7b0846704263f31e5990d

f0e7a8003b676a321abb4c3f158c0ead59fa2193e25285808f30504b340345a3

14a9ba638c728ba5ff58cc8220da65cb36ecf1dc507272f6a601c6b8e81cc9ab

1af64a27f6bd87cbd380cb838d6c8c06696f9497c246fe348d5af1bbc17f6122

320933c38d22ef6e76ca4866c11b33cbf245976661410c5ecef5dfc47e0b5fd8

6e10d2cad7d80003c55c8f9e464b6a19ea9f4be74d9d2253899441998e05cec5

8ac5e935bbeefa876f82d11054455a8fb01a61d283e2daa05d0e9edf14d334ad

3027d58dd2391de774d1a29617cbfe71255d4dd7f170b3ddfdfdb75ebbacda4a

74a112dc5a0c6960c4741d1f0fe8d8fc21cd37b23c5b34e6c1d667bd598ae95d

3ade8b6f7ac978ccf041268469fe1ad0465d6998d40f3d10b76efa16cd1caa71

6b39c1bdd3271ef116eaacf69e66fee6475770cadcdbab4c706b5ea77eb98230

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

Campaign

2026-03-roboat-addition

References

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

O3 blocks roboat-additions-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