What does the robase-install malware do?

The package is part of a malicious campaign, but was removed before the malicious code got embedded inside. 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

Which versions of robase-install are malicious?

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

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

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

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

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

Malicious package

robase-installPyPI

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

MAL-2026-2625

Immediate action

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

pip uninstall robase-install

What this malware does

The package is part of a malicious campaign, but was removed before the malicious code got embedded inside.

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

2.1.0

Indicators of compromise (SHA-256)

e1076baa8ca4cabd7ae4b1caafa04658a6f7a1c80f52d25de958412ec5d11661

7b187f6ea2c68694b9c87d49f1e1cd0b9f4fb3b82be853325ea6e1918f37d92c

4abd44ce2880baa56a51c2464425111ed4813def5b2a5967e5b3d4954a013c82

67f0c77cfc0e84191b044734a1cac746c23f76f99e332ff92873fcc157456506

8a3e4a8ccfcdcde414c74e65d9ba941a9e66b81c05fb50a15bcddb7c1502caf3

a3718ca22e10c23fecd31e8e5f58264968a18efeb9c0dfa2528b3e0938ce444e

c0275abf9696203282227774d8d03d6776bcfcf5927d1d62b107b6a2e31557cb

fd987d30e402e45a552f0c4dba7f3b3456909b20eb9155fe2edcfc5b0345584d

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