Which versions of databaseroboats are malicious?

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

How do I remediate databaseroboats if I installed it?

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

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

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

Malicious package

databaseroboatsPyPI

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

MAL-2026-2305

Immediate action

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

pip uninstall databaseroboats

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

2 flagged

0.0.30.0.4

Indicators of compromise (SHA-256)

dc1f844fef609b38cf45f4d47f4b11ead9ec2588dca7e619c873ff219dfb1e52

5b8193bb3e56929650df4e0fb0ba6ea3538bfa949936f56dbe9a9d111ae0bbbb

768d26c958373933d732729fc60fdbaeaf66d80206a00167933bedf4ac5f7fba

67bb2b905a4c43e78c7e7f6642d18a6e1ae5237ddcedbb274081d2f4c98cc8f4

9eb3db88480eae575b6bb1168c0fc538156c57bfd28c495046e6e294841063dd

5fe12252e6ac7b265cee74a65c00c5f6039d9122b2262f307487eb9560183b5c

758a06f15ef5917ecf964bae5fa46f084b028b69c8dd133acb90da972f6a6f09

9c85d133c07bc244ed6088bf0c36608861bf4ac882937e30587b5885a9658a1a

add4e9a40a09cecb550ee116cfea0a807dca5d29b89ced04ead850e89fba8073

a832c4c200232d723322ed83a62294c26dd5ef4f42dbdbf980ac02c6e830df17

c06ec4000bee0d3e4fabe62d22abd9a850c162cb713bd166ca393cc6c8ae198c

7771bc23478574c5a0edf12414a77def192b3530d44d98a47216ec68d5fbeb17

a22e385637d00b236c1ea03af5c6b022f85613983f17f4639934d1acf2d35ba1

1e93787c810495a6888e603122593fbed8cbe5c42e966c2e4d07f2b4f2315a57

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

Detect & block this

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