Which versions of dbindicator are malicious?

The following PyPI versions of dbindicator are flagged malicious: 0.1.0, 0.1.1. Treat any of these as compromised.

How do I remediate dbindicator if I installed it?

Remove dbindicator from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed dbindicator — how do I know if it already compromised me?

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

Yes — dbindicator is associated with the RLMA-2025-03582, 2025-07-db-indicator, RLUA-2026-00250 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 dbindicator 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 dbindicator (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dbindicator across your stack and pipelines.

Malicious package

dbindicatorPyPI

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

MAL-2025-6491

Immediate action

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

pip uninstall dbindicator

What this malware does

Code download and executes a remote script. At the time of analysis, the remote code just runs a notepad - as so classified as a pentest/research.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2025-07-db-indicator

Reasons (based on the campaign):

Downloads and executes a remote malicious script.

Malicious versions

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

aa6b8225435eda3fb1c7273231331a4cb3b7a26cb8cd94b79de54c53da535c83

6d464c0a78e51cd0193ba5593a88daf3c4e572b5cd0bf486a569507908132b29

7728e8fd1f3038b080b037908fea583383e6418d0aeb819e4b41b2b812b0b9d4

0fd9f69acd5115e0be5feb673467a2b78423f64e7479b6da7d7a50a5760c3b9e

5e4a59ee93b85fc7663648f06042c2b76816a8fe9615dfdb96f1b210a48c791e

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dbindicator (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dbindicator across your stack and pipelines.
If you installed it — respond
Remove dbindicator from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If dbindicator 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 dbindicator 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. dbindicator on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-035822025-07-db-indicatorRLUA-2026-00250

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks dbindicator-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring