Which versions of dbzy-tools are malicious?

The following PyPI versions of dbzy-tools are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate dbzy-tools if I installed it?

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

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

Yes — dbzy-tools is associated with the IN-MAL-2026-008612 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 dbzy-tools 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 dbzy-tools (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dbzy-tools across your stack and pipelines.

Malicious package

dbzy-toolsPyPI

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

MAL-2026-7023

Immediate action

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

pip uninstall dbzy-tools

What this malware does

The package advertises itself as a network debugging tool but its CLI and modules compose a remote-access toolkit. The dbzy-tools console entry calls core.start(config_url) which fetches JSON from a caller-supplied URL via urllib, base64-decodes the payload field, and passes it to exec() with no integrity check — arbitrary Python code from an arbitrary URL runs in the invoking user's context. server.py implements a paramiko-based SSH server that binds 0.0.0.0:2222, accepts hardcoded default credentials root/password, and spawns /bin/bash -i as an interactive pty for each authenticated session; paramiko is auto-installed via pip install at first import. frpc.py downloads an frpc reverse-proxy binary from a caller-supplied URL via curl, chmods it 0755, writes a config that tunnels a local port to an operator-chosen remote frps server, and launches it — providing a NAT-piercing path back to the SSH shell. The combination of remote-payload exec, listening SSH-to-bash bridge with default creds, and outbound reverse tunnel is a complete backdoor/RAT toolkit packaged under a benign cover.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

a0432a46ed92acb897826fc16d26cba900bd3d18f0de5baa7f2909a44d9ec625

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 dbzy-tools (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dbzy-tools across your stack and pipelines.
If you installed it — respond
dbzy-tools 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 dbzy-tools 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 dbzy-tools 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. dbzy-tools on PyPI has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-008612

References

pypi.org

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dbzy-tools-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