Which versions of dbnodeindicator are malicious?

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

How do I remediate dbnodeindicator if I installed it?

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

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

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

Malicious package

dbnodeindicatorPyPI

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

MAL-2025-6492

Immediate action

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

pip uninstall dbnodeindicator

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)

c85e50ef495fafd9089db0b04bd10f6e78ebae729b6a8331fe7fd19df4eab06b

583171c72fccbc14a50135c6e8cde528e93a43317676f1822cc918d5878d23a6

0ca31ed82ece767a66ae60f44cfb3e36aa54f84e952217e36376f6519ac1f777

10b02e3bcba5234a3604d099f93839353167aff90af04c167fc620be87bc652d

82c859f02851c6e743552d9ae603534b4e23da25f4185f8503ee9aedd01d9dc0

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 dbnodeindicator (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dbnodeindicator across your stack and pipelines.
If you installed it — respond
Remove dbnodeindicator 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 dbnodeindicator 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 dbnodeindicator 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. dbnodeindicator 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-035832025-07-db-indicatorRLUA-2026-00251

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks dbnodeindicator-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