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 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-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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chain-devkit (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chain-devkit across your stack and pipelines.

Malicious package

chain-devkitnpm

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

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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chain-devkit (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chain-devkit across your stack and pipelines.
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 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-devkit 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-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