Which versions of databaserotacos are malicious?

The following PyPI versions of databaserotacos are flagged malicious: 0.0.4. Treat any of these as compromised.

How do I remediate databaserotacos if I installed it?

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

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

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

Malicious package

databaserotacosPyPI

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

MAL-2026-2490

Immediate action

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

pip uninstall databaserotacos

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

Indicators of compromise (SHA-256)

d50833ec383a82f726fdf4acd90e8206e4ca5881e05769b72eb5a7484fae40a3

6c4930bbf42475b62cfc2e5d80ac13a4f54c4061102527fb78d1527ea38acacc

c984d982a49ccf0cae98e40eccd781f1a08b242dbca9c570ab6774d32d3c20d3

a7a512c8401744cd700d018d71d92b1b0303230caee0140ad370c5ca07f1eec2

9510d1ce4b68182fe0f028bdf10fe844a64b3e86e8b59ca28716846a191253cb

04d640be20e9d2ff55f7682d535f6fd56b67b50008307c2e41986d6b31d4bfa4

acb6832c76b97dee95d51142aa8cd0555721af75764396832fe436cc3a341f5d

18b978c2c8dd92202cd9a1ec74dd74ae774fdf146845508f70018bee4401e366

23d642994456ba6ab251ee85c69f883f818aea94f874b9a7c0d9e66c19d25179

7b4766264ef8e9ad08e94e6edb22e5f36fb511d03f6041b71974d3a54f598f8b

169595db71421daf67fe88d4f311353e53e99b2ed08ab48e9b028e88625f82b7

000f3f9e602a6eeb98234da16e77fd8ce90b718c2974e90d9eecf707fc03c0b0

c2e50b1137e348e4e65a9bb15d977b6d1be4eb1aa39997908618ddc6323f7840

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