Which versions of node-db-indicator are malicious?

The following PyPI versions of node-db-indicator are flagged malicious: 0.1.2. Treat any of these as compromised.

How do I remediate node-db-indicator if I installed it?

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

If node-db-indicator was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is node-db-indicator part of a known attack campaign?

Yes — node-db-indicator is associated with the RLMA-2025-03655, 2025-07-db-indicator, RLUA-2026-00559 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 node-db-indicator across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for node-db-indicator (version 0.1.2).

Malicious package

node-db-indicatorPyPI

Advisory published Jul 11, 2025Updated Mar 19, 2026

node-db-indicator is a confirmed malicious PyPI package (MAL-2025-6558) that executes malicious code on install (malicious version 0.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in node-db-indicator (PyPI)

MAL-2025-6558

Immediate action

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

pip uninstall node-db-indicator

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

1 flagged

0.1.2

Indicators of compromise (SHA-256)

00738b29b8eee02047ce9ebce33b9ca4d6904f85763bd51cb5a13b2485ac1e49

38e66e7a73e04a99ca6362fff3930ec88b514cb1a9e1af86ba64cfbd1973f2d0

7c9a18fe9ea04133e7de33313046092ffb5e8ccef6c1bf5f44e9b6d5e3835aa2

d1391b2c1038576602b77ea99f80117f9025d8575bacf1cc93f7a7463ed44c42

ddf0e4fd1e3a693d12e61c2f814a90812348fc8c4297632800ba1dcfd8996e19

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for node-db-indicator (version 0.1.2).
If you installed it — respond
Remove node-db-indicator 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 node-db-indicator was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. node-db-indicator on PyPI has been identified as a malicious package (version 0.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-036552025-07-db-indicatorRLUA-2026-00559

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks node-db-indicator-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

Explore

All malware advisories How O3 detects malware Vulnerability database