Which versions of coremeshnode are malicious?

The following npm versions of coremeshnode are flagged malicious: 2.4.5. Treat any of these as compromised.

How do I remediate coremeshnode if I installed it?

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

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

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

Search your lockfiles and build artifacts for coremeshnode (version 2.4.5).

Malicious package

coremeshnodenpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

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

Malicious code in coremeshnode (npm)

MAL-2026-2751

Immediate action

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

npm uninstall coremeshnode

What this malware does

The package coremeshnode was found to contain malicious code.

Malicious versions

1 flagged

2.4.5

Indicators of compromise (SHA-256)

2722b134cc6a997ba50501b11c1b71f9e8e689875fcf32814586db4b7ce46a4f

73581f65b19dbb45cdfe8c3ab269c673d7c062e4a1a76e7c85f6a4d6bc09a252

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01930

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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