Which versions of coremesh are malicious?

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

How do I remediate coremesh if I installed it?

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

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

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

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

Malicious package

coremeshnpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

coremesh is a confirmed malicious npm package (MAL-2026-2750) 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 coremesh (npm)

MAL-2026-2750

Immediate action

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

npm uninstall coremesh

What this malware does

The package coremesh was found to contain malicious code.

Malicious versions

1 flagged

2.4.5

Indicators of compromise (SHA-256)

c9f071802b46a674f3009a0d25071c9808e980303e43b339e2b4174f363a4e51

2e1c5c73eed4959ff3773bce8dd6ceee55a4cb517758013fcfb3075859cb05f5

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for coremesh (version 2.4.5).
If you installed it — respond
Remove coremesh 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 coremesh 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. coremesh 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-01929

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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