Which versions of databasesupalake are malicious?

The following PyPI versions of databasesupalake are flagged malicious: 1.2.0. Treat any of these as compromised.

How do I remediate databasesupalake if I installed it?

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

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

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

Malicious package

databasesupalakePyPI

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

MAL-2026-2559

Immediate action

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

pip uninstall databasesupalake

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

1.2.0

Indicators of compromise (SHA-256)

ec2327cbf40d485fa6ea474f7cdbe9a352e0a2b27969816ffb22fee6244a8b96

5325afc74822eb4bfc9061310dd9c87843965ef0cc6ca1a201e413d9a55e0303

78dbe2b5e300604ea36dc85a6b0e9eae4e92b7b3729de10b3951f5e3bfc7729b

f4b3270ba4196342bea538d3e21fa6f6b3194f06728225d473f67a3d3cb8f82b

cb1eba033456835f7b00845bce0ead1b36c9e35290aa16aedaea93455e14b22c

e664acea271a339cf75f32b229ff0782adbb8da3185716c00c5ef55c082ca700

ca5623f2d11e9f57386e6d80dbd3b4845641412396826d6d178c7e24d477421f

f6c29d5121b6ec037546dab85892382356d58fa50d27b678a210b9f2605ac454

f9527b3a54850d25169f5bd659290d4083142fc12ba5eb5c09f6f3296e8a4ff4

e40bbb7096e45ff0c695c09e2049e08a652d9279aebd4cdf6c3e8e909bd7e05c

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