Which versions of chai-proxy are malicious?

The following npm versions of chai-proxy are flagged malicious: 2.4.2, 2.4.3. Treat any of these as compromised.

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

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

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

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

Search your lockfiles and build artifacts for chai-proxy (2 malicious versions).

Malicious package

chai-proxynpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

chai-proxy is a confirmed malicious npm package (MAL-2026-1684) that executes malicious code on install (malicious versions 2.4.2, 2.4.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chai-proxy (npm)

MAL-2026-1684

Immediate action

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

npm uninstall chai-proxy

What this malware does

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

Malicious versions

2 flagged

2.4.22.4.3

Indicators of compromise (SHA-256)

a7e5ae44fbed28810ffa7bed21dd831c43272b110c0b17296cf7cd3c42c9bf37

19abbfde079ce3f23e7c34a0234c9d56fc21ea648c3136c5034128e5d463d036

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01189

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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