Which versions of robase-setup are malicious?

The following PyPI versions of robase-setup are flagged malicious: 2.0.0, 2.1.0, 2.2.0, 2.3.0. Treat any of these as compromised.

How do I remediate robase-setup if I installed it?

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

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

Yes — robase-setup 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 robase-setup 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 robase-setup (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging robase-setup across your stack and pipelines.

Malicious package

robase-setupPyPI

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

MAL-2026-2864

Immediate action

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

pip uninstall robase-setup

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

4 flagged

2.0.02.1.02.2.02.3.0

Indicators of compromise (SHA-256)

3fcd831a04f3c23efde7a365717e715cec5c6fb5211d26e5d76ace539abb06bc

98af92d37a5a146cd2f4e6c8ca5277c06a7f76e092b360bf660435fdeb1e3fa4

6e530b0918f5a3d671dfb6f0b77a84c953f4dc6ec3d49d4c0bbf7d760087526f

1ebbd242aa9e4e975fbb920d767cc9445a9cf2050d59840393fb3d79d8857cf0

b771982e3219d7b525eca7666498bce8faa0da7ac5c2d1a3f7d94a7d83112dfe

b4fa538dae28e6a90997a4b51284b4d2cfd0e9028188ede08c803477939661ff

1a65034546d39892500fa8b3a0421969d6cacf91d723809c030df5b619f05226

2166fe78f29ede1d3fecfe133fc0a4c9ff89c2035acb242eb5e522e25cdce3a6

b75a6767650451005ec5477446b63e91d787b949421dda61e3edc93b041e1613

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 robase-setup (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging robase-setup across your stack and pipelines.
If you installed it — respond
robase-setup 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 robase-setup 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 robase-setup 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. robase-setup on PyPI has been identified as a malicious package (versions 2.0.0, 2.1.0, 2.2.0, 2.3.0 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) · reporter

Detect & block this

O3 blocks robase-setup-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