Which versions of chai-pack are malicious?

The following npm versions of chai-pack are flagged malicious: 1.1.7, 1.1.9, 5.1.0. Treat any of these as compromised.

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

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

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

Yes — chai-pack is associated with the RLMA-2025-06089, RLUA-2026-01178, RLUA-2026-01726 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-pack across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for chai-pack (3 malicious versions).

Malicious package

chai-packnpm

Advisory published Dec 23, 2025Updated Apr 1, 2026

chai-pack is a confirmed malicious npm package (MAL-2025-192725) that executes malicious code on install (malicious versions 1.1.7, 1.1.9, 5.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chai-pack (npm)

MAL-2025-192725

Immediate action

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

npm uninstall chai-pack

What this malware does

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

Malicious versions

3 flagged

1.1.71.1.95.1.0

Indicators of compromise (SHA-256)

19978df65270f651588b97e4f4dc4c7faa561c93925fda06cbe4d75b75a94196

a153ef79c99f8b960c8e0557a16cb187571a31c3d4c2479e177ab630b36b6af6

e971cc20e649cc965be323ec45888434a827875cd9aca6ea38dec784c5716c4a

b5780e0f5c67426d679ef2fceb31dbd8c1093f8b1d81ec55583989355dc7a3f3

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06089RLUA-2026-01178RLUA-2026-01726

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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