Which versions of node-neurograde are malicious?

The following npm versions of node-neurograde are flagged malicious: 2.4.7. Treat any of these as compromised.

How do I remediate node-neurograde if I installed it?

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

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

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

Search your lockfiles and build artifacts for node-neurograde (version 2.4.7).

Malicious package

node-neurogradenpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

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

Malicious code in node-neurograde (npm)

MAL-2026-2379

Immediate action

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

npm uninstall node-neurograde

What this malware does

The package node-neurograde was found to contain malicious code.

Malicious versions

1 flagged

2.4.7

Indicators of compromise (SHA-256)

5e6d2cdba70eafebb453ebde0da41b7f7cb8020c5c4e41ba19052a7fbadf2a65

87deda0e4e9f843c759c9e8f0b41cfdf3a1f9451f1a53ccaf2a32c092a706180

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01798

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks node-neurograde-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