Which versions of databasetrace are malicious?

The following PyPI versions of databasetrace are flagged malicious: 0.0.5, 0.0.6, 0.0.7. Treat any of these as compromised.

How do I remediate databasetrace if I installed it?

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

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

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

Malicious package

databasetracePyPI

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

MAL-2026-2542

Immediate action

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

pip uninstall databasetrace

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

3 flagged

0.0.50.0.60.0.7

Indicators of compromise (SHA-256)

3595549c5e7d83e6c4d0b227fa42882622762067b42be28b3c4943f37eb98201

6f5d3117e59dfe219ba8a1ea737a74da80cb60a5ee31610f90511cf995af2913

144ff96bc84711f9be4c580e9d4b4cdcc650d9faf2f6ca9008ca34234d888805

efd5090449736ceb721792535c2ca2f5cd30b7d176261b0af794d503f5164dee

70b27e8603b76a2ccadbc181b86c1f5e1db51c7996444f7c965f41ed0892faae

95750c7884ef3c200d1154e2e628629b2296d74ee52043f3723031824813b8bc

162e43aa3055c8c23707188dc5892838e36f9dd33da8bbf8843d006a3fa93275

1119f419c3be73d0eb0fedd4ef1cc421d168abb18875dc6b4c2f5bc5f6f24b83

ad26b682187fa901dfca0d7607858054534cb075b3fb1c3e1891215a98077498

7a4428354e53afd1715b1b07df0716638c765a456f05f8ab4676337b9c4d0737

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