Which versions of chai-conf are malicious?

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

How do I remediate chai-conf if I installed it?

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

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

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

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

Malicious package

chai-confnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

chai-conf is a confirmed malicious npm package (MAL-2026-1678) 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-conf (npm)

MAL-2026-1678

Immediate action

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

npm uninstall chai-conf

What this malware does

The package chai-conf was found to contain malicious code.

Malicious versions

1 flagged

1.1.7

Indicators of compromise (SHA-256)

1a2f8b7ad15fd9cbbc759c89f35c0114bc2aefba62e50ef26f108b916d744fc6

e77f30f15e3e699b15abf8ebd6bac4a15f8032d0411ab2b445f056ff0228b844

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for chai-conf (version 1.1.7).
If you installed it — respond
Remove chai-conf 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-conf 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-conf 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-01173

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks chai-conf-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