NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Part of a larger attack: 2026-03-roboat-addition published 52 malicious packages. See the full campaign →
Malicious package

rogiantPyPI

Advisory published Updated

rogiant is a confirmed malicious PyPI package (MAL-2026-3332) that steals credentials and exfiltrates sensitive data (malicious version 2.4.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rogiant (PyPI)

MAL-2026-3332
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall rogiant

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
2.4.0

Indicators of compromise (SHA-256)

c7f7e1dc50782abed477c5013c8a732e952d747ffa770f399571ff468699b8f3
eb9c60cea480218a72a41cb3e6901eaac55bcc291ccb18a65bd5e5395ea795a9

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for rogiant (version 2.4.0).

  2. If you installed it — respond

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

  3. Did it already run?

    If rogiant was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. rogiant on PyPI has been identified as a malicious package (version 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) · reporter

Detect & block this

O3 blocks rogiant-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

rogiant (PyPI) malicious package — MAL-2026-3332 | O3 Security