Which versions of roboat are malicious?

The following PyPI versions of roboat are flagged malicious: 0.0.1, 1.1.0, 2.0.0, 2.1.0, 2.20. Treat any of these as compromised.

How do I remediate roboat if I installed it?

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

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

Yes — roboat is associated with the 2026-03-rowrap 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 roboat 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 roboat (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging roboat across your stack and pipelines.

Malicious package

roboatPyPI

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

MAL-2026-2121

Immediate action

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

pip uninstall roboat

What this malware does

During installation, the code attempts to download and start malware.

Connected with the campaign based on the time correlation and other packages published by the author.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-03-rowrap

Reasons (based on the campaign):

Downloads and executes a remote malicious script.
malware

Malicious versions

5 flagged

0.0.11.1.02.0.02.1.02.20

Indicators of compromise (SHA-256)

f04db4869c9e981873683b537f335c1f25c7c17c283315859699855a9c20816b

e94bd912e703150e428eafa84e1f5aea427c9afe6c30f16ff2b5aca6f52c55b1

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 roboat (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging roboat across your stack and pipelines.
If you installed it — respond
roboat 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 roboat 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 roboat 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. roboat on PyPI has been identified as a malicious package (versions 0.0.1, 1.1.0, 2.0.0, 2.1.0, 2.20 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-03-rowrap

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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