Which versions of chain-guardian are malicious?

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

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

chain-guardian is a typosquat — you almost certainly intended a legitimately-named package. Remove chain-guardian, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed chain-guardian — how do I know if it already compromised me?

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

Yes — chain-guardian is associated with the IN-MAL-2026-010201 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-guardian across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for chain-guardian (version 1.1.0).

Malicious package

chain-guardiannpm

Advisory published Jul 13, 2026Updated Jul 13, 2026

chain-guardian is a confirmed malicious npm package (MAL-2026-10433) that typosquats a legitimate package to trick installs (malicious version 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chain-guardian (npm)

MAL-2026-10433

Immediate action

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

npm uninstall chain-guardian

What this malware does

chain-guardian presents itself as a mocha gas reporter (typosquatting eth-gas-reporter) but its main entry index.js contains an always-true gate (var opt = 1; if (!opt) {... } else {... }) that forces construction of the reporter to invoke utils.connectNet. connectNet resolves lib/syncResolve.js and spawns it via spawn('node', [u_src], { detached: true, stdio: ['ignore'] }) followed by progs.unref(), so the child continues running after mocha exits with its output suppressed. lib/syncResolve.js fetches http://check-server-state.vercel.app/server/v2 over plaintext HTTP and, on a 404 response whose body carries a token field, passes that field to new Function('require', error.response.data.token) and invokes the resulting function with the real require, giving the remote host arbitrary code execution in the developer or CI Node process. A duplicate benign Gas reporter function is defined but never exported, serving as cover for the dropper path.

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

1c281292766d55cda3ff1b006154150aa05d567a4f8115534788ffbbc014f3e7

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for chain-guardian (version 1.1.0).
If you installed it — respond
chain-guardian is a typosquat — you almost certainly intended a legitimately-named package. Remove chain-guardian, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If chain-guardian 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. chain-guardian on npm has been identified as a malicious package (version 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010201

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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