Which versions of robase-api are malicious?

The following PyPI versions of robase-api are flagged malicious: 2.4.0, 2.6.0. Treat any of these as compromised.

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

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

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

Yes — robase-api 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-api 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-api (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-api across your stack and pipelines.

Malicious package

robase-apiPyPI

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

MAL-2026-2699

Immediate action

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

pip uninstall robase-api

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.4.02.6.0

Indicators of compromise (SHA-256)

32170773fbd5fab5b2494de72ce601e7b43d9b5c21f36b9bc26a6ada40024de6

4d97cc259bc73a0a5a0292ba0cae0c37e43eafa10dfb10cac161800ef9143cab

6d2a055a1de4f40f1586d6981166f4dc918ce1a58e66b2bd425f309eab84a1d3

7fafced5c3039a3796627eff716969a65930e8065b5a968330d84e97238e45de

b9b8f159a5be22bf6b398e97504f2b02004a2377f396b988f51ffeb09dcbf5c8

bd35ecb4add45a071f928aaf2086600f13f6a75d359ee23a85647c9b2d04e607

31679d3f6c5b3f9a64ff8d68ede76d303c46cb8127c11abea7a3b8d46d59686c

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-api (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-api across your stack and pipelines.
If you installed it — respond
robase-api 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-api 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-api 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-api on PyPI has been identified as a malicious package (versions 2.4.0, 2.6.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-api-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