Which versions of robase-help are malicious?

The following PyPI versions of robase-help are flagged malicious: 0.0.9. Treat any of these as compromised.

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

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

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

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

Malicious package

robase-helpPyPI

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

MAL-2026-2561

Immediate action

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

pip uninstall robase-help

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

Indicators of compromise (SHA-256)

1d0d99815707deee79d693ff3da777633aa93c69977335456dd51c9dc61125ab

fb4e9d859fcd05a680d606e66b8d4263121b41af3f9b64183846e0eac315b643

b83143e22b0a815d6a2702f547ae9f4620ee086c8b9360a0d60ff2ed2186d56b

074251c6c776ba443e53017a18d29be7076b9a45d02ee96c72c0f8065327c111

1a649a20a45ce164282d59e0c5cc707ead1e1d5ea2a3eac7f6266ecedfc05fd1

20dc9d7eb6f767f1a3e71a401d3eecce3915402dcf4c06b5ea255be5db885902

1ac200c2845d2dec548c83f98b2c228785ef4fb20eabc70873dedf06e6c46061

a8a398e3dd2571bf1ef9cd0dcf27a14322e950898d17a64651f722ca3d5738cc

76bc3228cfa9c3347b43db01694b323bcd0e2e169bfdf72526f5f58506521a7b

52ea67e3b46f596eeb1389d804015e92a1ce702ecc0abddadeaa21c15ef438a5

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