Which versions of roboat-util are malicious?

The following PyPI versions of roboat-util are flagged malicious: 2.30, 2.40. Treat any of these as compromised.

How do I remediate roboat-util if I installed it?

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

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

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

Malicious package

roboat-utilPyPI

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

MAL-2026-2142

Immediate action

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

pip uninstall roboat-util

What this malware does

During installation, a malicious executable is downloaded and run.

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

2 flagged

2.302.40

Indicators of compromise (SHA-256)

869ea4b94181bc5ef23562a4d749b462fb7079112cca74072ee9036fb397921f

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