Which versions of databaselooks are malicious?

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

How do I remediate databaselooks if I installed it?

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

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

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

Malicious package

databaselooksPyPI

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

MAL-2026-2501

Immediate action

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

pip uninstall databaselooks

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)

a2d51aa3f1476f1040efea0eec94f2174e78c1be60790df6f57ea842d29e85ce

c6d213db0f9847cd8570484aa0c4076e0a4c42bc0b09b87a4c4659913cfa18ec

9fa64b720dbbdf55e88fe78db9449b74d0d4e90115270f831a13a0194cb9eba2

bcc588d8d22a712d7b5d7d407f49c50e32ebb9008420be7508aa97a8e01fcefd

dd73d73ace43286d9d97ccebb1f758b52cfd114774b862c5b568a7d1151d0112

4f443e06b0c105d0b59f604cb02c3a11da251029b8ad3669180aa167add70bef

3a66b2721eff8703a863876c6ff742e965c068628ecd6243db0396557e207e98

c10f7a8f51f2d38e963ca6f7f2cff95ac204beb8918c62b89421e8efca83bb31

42a61f1362b384d2abfeb3e6f7e5ad1ec893545028bcf2fc9ce4af359a5bf69d

60956e3a22c5b5627671bb4044a1baaa845b37bc6ce4a85344cf22273087f4af

98ccd403883d0cdf4cc5689c853de96def2ec8deab0110e39aba05ca79997b8f

2dc2185461e459e56a6c2efe4a44a25abfb6295352f1190c4aa2049e3c6a9728

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