Which versions of robase-fallback are malicious?

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

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

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

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

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

Malicious package

robase-fallbackPyPI

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

MAL-2026-2562

Immediate action

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

pip uninstall robase-fallback

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

Indicators of compromise (SHA-256)

f239c0ba3898ce3ed99dd999a840e6a5650c026ccd44bed981e6e861c59bd193

f119207ff2e84e17b2a4a4e602f696a794a179d96a7e364aed4bb0305ba2648e

a90a9e6e638fef782e18c99b5ab69341776385c7c7e6000af01a6b0fd2c3b0b6

aaee9006978a509feafab13a43d293c4f7a1cdd74ed1dc4bdebbdd88c7ed380f

0f3b0fefd27f4d5602be73cfd33f1cc808f255dba9bba8115b7099bc2c4e3503

f26837afe3c3766a55b85f51b9cc4c5ca5aed7d2fee4b54eeb92bf390fda4f29

e586f99c581b50affc07b330fa519fdbd7c588e0581e4bde8b06486b91ef166e

b1351470addbbb9549cddf0a46c042311741d8452635e89c97191356cfc004ac

2436dae405ed10cdccca5c5d5d47c44471f2e2d398ebe4cbea08c27922794d23

1e3483e8747b2f91ec5bf3477de578837df7bb5b66dc7024e691281bcf005b07

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