Which versions of nodecognivault are malicious?

The following npm versions of nodecognivault are flagged malicious: 2.3.5. Treat any of these as compromised.

How do I remediate nodecognivault if I installed it?

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

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

Yes — nodecognivault is associated with the RLMA-2026-01799 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 nodecognivault across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for nodecognivault (version 2.3.5).

Malicious package

nodecognivaultnpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

nodecognivault is a confirmed malicious npm package (MAL-2026-2380) that executes malicious code on install (malicious version 2.3.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nodecognivault (npm)

MAL-2026-2380

Immediate action

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

npm uninstall nodecognivault

What this malware does

The package nodecognivault was found to contain malicious code.

Malicious versions

1 flagged

2.3.5

Indicators of compromise (SHA-256)

3d4feb64b3823832298b50d36a5e7ba335ecdbff4b9acb814efbdfe794f56054

7709482c6e8d04dee2a9310780eff8f0f31cb64800273088f08a5cd1a8570c0a

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for nodecognivault (version 2.3.5).
If you installed it — respond
Remove nodecognivault 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 nodecognivault 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. nodecognivault on npm has been identified as a malicious package (version 2.3.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01799

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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