Which versions of chai-as-sync are malicious?

The following npm versions of chai-as-sync are flagged malicious: 1.1.7. Treat any of these as compromised.

How do I remediate chai-as-sync if I installed it?

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

If chai-as-sync 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 chai-as-sync part of a known attack campaign?

Yes — chai-as-sync is associated with the RLMA-2026-01158 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 chai-as-sync across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for chai-as-sync (version 1.1.7).

Malicious package

chai-as-syncnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

chai-as-sync is a confirmed malicious npm package (MAL-2026-1672) that executes malicious code on install (malicious version 1.1.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chai-as-sync (npm)

MAL-2026-1672

Immediate action

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

npm uninstall chai-as-sync

What this malware does

The package chai-as-sync was found to contain malicious code.

Malicious versions

1 flagged

1.1.7

Indicators of compromise (SHA-256)

c10f76e1ccd95a075a0a07513bb12fa6dd7e4f1099556d4e90d48884195c46c0

201c3097a1417370d6190e60489ac7894d63b574004eaa2b069958131ea2eda0

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01158

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks chai-as-sync-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