Which versions of nodex-db are malicious?

The following npm versions of nodex-db are flagged malicious: 8.4.13, 8.5.10, 8.5.11. Treat any of these as compromised.

How do I remediate nodex-db if I installed it?

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

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

Yes — nodex-db is associated with the GHSA-28w8-cpp5-g448, RLMA-2026-01800, RLUA-2026-02005 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 nodex-db 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 nodex-db (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nodex-db across your stack and pipelines.

Malicious package

nodex-dbnpm

Malicious code in nodex-db (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1960

Immediate action

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

npm uninstall nodex-db

What this malware does

The package nodex-db was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

3 flagged

8.4.138.5.108.5.11

Indicators of compromise (SHA-256)

8553471928a4ec525f93f26d6207bd42e251966d69861965e35f9ee97038d141

851296e1195af851909142fcb22d46855f226b735b02a1510e0ae9015f9c9824

f309f059637c9cb7368f9cd1afcd392d112f0d8758742e27f067c86fe1107d05

b09ca630a0853429c770f700efe2560472b4b85110509f149960f0b09cbebbd0

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

Campaign

GHSA-28w8-cpp5-g448RLMA-2026-01800RLUA-2026-02005

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks nodex-db-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