Which versions of chain-coremesh are malicious?

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

How do I remediate chain-coremesh if I installed it?

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

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

Yes — chain-coremesh is associated with the GHSA-mgm3-4q53-38p5, RLMA-2026-01920 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 chain-coremesh 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 chain-coremesh (version 2.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chain-coremesh across your stack and pipelines.

Malicious package

chain-coremeshnpm

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

MAL-2026-2222

Immediate action

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

npm uninstall chain-coremesh

What this malware does

The package chain-coremesh 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

1 flagged

2.3.5

Indicators of compromise (SHA-256)

7c22f3e9c994c2b163ca8dc9cfdd501768a8ed0163ccc7c9fde8160ace616303

53c78d25a9b5c960f74dda3653e6f237df054e60b0234511fa4e9fe3d650a00f

8466a3aed3b7323c4df50fbebba1e1b5c304b9a0848efd8feeeff868caaa34c6

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 chain-coremesh (version 2.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chain-coremesh across your stack and pipelines.
If you installed it — respond
Remove chain-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 chain-coremesh 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 chain-coremesh 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. chain-coremesh 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

GHSA-mgm3-4q53-38p5RLMA-2026-01920

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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