Which versions of database-roblox are malicious?

The following PyPI versions of database-roblox are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate database-roblox if I installed it?

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

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

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

Malicious package

database-robloxPyPI

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

MAL-2026-2289

Immediate action

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

pip uninstall database-roblox

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

Indicators of compromise (SHA-256)

b66c65a2aaea77057240357862efea9ac3af04b4e6f65b24a070291b406e1b6f

12a6e8c2d701596172a40974207770687437cb552cecc8108a1f256546d810b5

b59069109fc624a8cf4223c9fb3660d240793b6daa6588376964f9eeb80efbf6

14ee770bea712aa55baa2d0146accdd8e77f5454dc5eb8aeac005412460bceee

16d80c9007277589dea462fc1cc169a1bd54c4229aa8566c7c74996a090c3943

4ad5f1aa4a301cd222e5b1216c2cefc73100be5462a9f95d776fff8ca7f227d7

c47cc65cf4383aa4252e212df2cd80308baf9068f0bec0fd545d137533f96932

bc72e398d8a27feaf630ecd5c3f852b452ad895a1e0a104abbc87da277e3bfc4

683d00b22d40cb3f96b259b97c4b5784713d7ec53246f4d8472f1b0df8a136b7

e349f950d8ce53578ed27c8d5837c33c28a4489a739882d247a173abc944fa01

2636fbe91dd452be0f38efab2d3a6d2d84b998d7e526e0312e542452f667fb6d

32852a445d842b12297fdedbe3361405a378bef82d8b74804021ce34ed744f5e

c256ad43bf9b454c66d182980f8d94f536d61b924d4c1b3a0d4bd19215f1db91

0ae14ee58ad20a61b4e49eef7e69b63f8b38c039a1c3019b20d5cc801abc9c7a

06d1ae956ab7d10ec84ea04194e4031df1804b5a028530267b00468a9a659d9d

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