Which versions of databasetapes are malicious?

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

How do I remediate databasetapes if I installed it?

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

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

Yes — databasetapes 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 databasetapes 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 databasetapes (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 databasetapes across your stack and pipelines.

Malicious package

databasetapesPyPI

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

MAL-2026-2494

Immediate action

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

pip uninstall databasetapes

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)

b80211cd83eadafb46b131727e00759d3766bc1e1d2c25d399ddc9150ecf32e1

404d8a348eab93d01fb25c7782536976b78123759077cf06cd939ddf6cba9bf8

c9f0aa6e7bc1dfc5b7942d45f87c1f69d8c0fa080e76964ea29372d9a380b8e0

512fe505678cab5ff24d49099ca6215c5f7679c2be26aa76dce90ad7cca667a3

d859d21aa59dfad2efc5c2f98253cd1cc808621fb3b7525037c104324e27dfe8

44fce440170ca8e8b90d8fdb75421d9be9c753218d0a7d2cb838d30ba15e901e

8c30e1b9bed2d235328a895cefb54920161d60ea32362b18e96b88e6371807fa

6f8ecbeae6ee8cb6c58135e4891b8fb054fe8ca712b28308ad5530b1b8459409

d477d1456dd4decf7cce673e1736d404a3a19bf45e7f7897f5fbdbd03ce58bc4

43339c3b604506e776dddf08eac0e5a125696a11d7f5ff8363ba733110ea18c2

1568296598ea7ee06cb5cc16ae5720a1f6aaa6c0cae6e66d77c9fb960b1814fc

55d387c19ad2d102bd08070063219d97abfab9cfc9ccb323b6d6eba57f42559b

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 databasetapes (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 databasetapes across your stack and pipelines.
If you installed it — respond
databasetapes 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 databasetapes 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 databasetapes 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. databasetapes 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 databasetapes-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