Which versions of chain-promised are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for chain-promised (version 2.3.5).

Malicious package

chain-promisednpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

Malicious code in chain-promised (npm)

MAL-2026-1688

Immediate action

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

npm uninstall chain-promised

What this malware does

The package chain-promised was found to contain malicious code.

Malicious versions

1 flagged

2.3.5

Indicators of compromise (SHA-256)

acc89c904a4f60a33aaac1c2445eab0d1c261f53713be8532abb549bd1b2ccc8

2fd6ee3247632a88a25b8059314727f1757ed1163081b133945fbe4af59e5d28

Detection & response playbook

Malicious package

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

RLMA-2026-01202

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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