Which versions of chain-devkit are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for chain-devkit (version 1.0.0).

Malicious package

chain-devkitnpm

Advisory published Jul 14, 2026Updated Jul 14, 2026

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

Malicious code in chain-devkit (npm)

MAL-2026-10531

Immediate action

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

npm uninstall chain-devkit

What this malware does

The postinstall script fetches YAML from https://chain-devkit.com/config with no version pin, hash, or signature check, then parses it with js-yaml 3.12.0's yaml.load, which honors!!js/function and!!js/regexp tags and constructs Function objects at parse time. The parsed object is written to chain.config.yaml and re-loaded at require() time via the same unsafe loader, giving whoever controls chain-devkit.com a live channel to inject arbitrary JavaScript Function objects into installer processes at every install and every require. Current index.js only reads scalar fields (chainId, rpcUrl, network), so code execution is not automatically triggered on today's config content, but the injected Function values persist in the on-disk config and would execute if any consumer or future package version invokes them. Publisher metadata is thin (atomicmail.io author email, fresh package with no history), and the destination host is controlled by the same anonymous publisher, so the fetch is effectively an attacker-controlled update channel bolted onto npm install.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

aabf751a767ad631ac38651254930d99c8ccb0feab8dc5c96b5d3ab243796ddc

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-010389

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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