Which versions of chain-promised-await are malicious?

Every published version of chain-promised-await on npm is considered malicious. Remove the package entirely.

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

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

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

Yes — chain-promised-await is associated with the GHSA-x7f9-fr3r-64w3 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-await 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-promised-await (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chain-promised-await across your stack and pipelines.

Malicious package

chain-promised-awaitnpm

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

MAL-2026-1320

Immediate action

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

npm uninstall chain-promised-await

What this malware does

Remote code execution via fetching code from a remote URL and Discord webhook usage indicates malicious intent. Single version adds to suspicion.

The package chain-promised-await 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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

b5b882a33fdd394ef7a848100d8ee39ef4c7f0747942b4bea86e38af5780c978

4c27a66657401c034b4b834e46e04b5474e23e430a5a8b6de6163c62a854a982

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-promised-await (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chain-promised-await across your stack and pipelines.
If you installed it — respond
Remove chain-promised-await 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-await 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-promised-await 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-promised-await on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-x7f9-fr3r-64w3

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

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