Which versions of robase are malicious?

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

How do I remediate robase if I installed it?

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

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

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

Malicious package

robasePyPI

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

MAL-2026-2543

Immediate action

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

pip uninstall robase

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

2 flagged

2.1.02.2.0

Indicators of compromise (SHA-256)

1cc5ff7fcb54bc2ef48ede2c38d4f55b93150053732dc8cb9871925c50138372

bfded752fed1c804f73f624d6828affe03a5ea0794afc6ae41b4a73415dd2c4b

f128f86ab257491fc121f6b5d630cf37776085c139f199ec930ec16a31691855

8f6bbc1a743e705c3718e98ba13f87d72e993663033dfd216dbbbc4391d0e886

4d469897db6162b29abf6430e28d72a840f67ab5834385646491e20703110863

d9a16d5214401339dfe3ab45d972a3bdecb4113b057bdb38636f485f176cbbe0

e56e89f7162dc13df32aa96904bebe457b796be43b472889fb943f9c9c64f209

bd084c330450f8d300c516ed0cb42bbeaabc9cd01e48d485bf09357f519dbbee

68f36f5b4fbeeb53f5c582ab56c3c002f172854a3a6f63504be5729af965b580

0271771769db0c66e93d014f8f5c66998f295997c2382019ecb894fce6075042

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

Detect & block this

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