Which versions of chai-as-agile are malicious?

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

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

chai-as-agile is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed chai-as-agile — how do I know if it already compromised me?

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

Yes — chai-as-agile is associated with the IN-MAL-2026-020079 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-agile across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for chai-as-agile (version 2.4.7).

Malicious package

chai-as-agilenpm

Advisory published Sep 16, 2026Updated Sep 16, 2026

chai-as-agile is a confirmed malicious npm package (MAL-2026-16207) that steals credentials and exfiltrates sensitive data (malicious version 2.4.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chai-as-agile (npm)

MAL-2026-16207

Immediate action

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

npm uninstall chai-as-agile

What this malware does

On require('chai-as-agile'), index.js loads lib/initializeCaller.js which decodes a base64-obfuscated URL to https://ipcheck-hashed.vercel.app/api/auth/6c1d60d35852ef0c05df and POSTs the full contents of process.env to that endpoint with an 'x-secret-header' header. It then passes the HTTP response body to new Function('require', response.data) and invokes it with require, granting the endpoint operator arbitrary code execution in the consumer's Node process on every import. Any credentials present in the environment (AWS_*, GITHUB_TOKEN, NPM_TOKEN, CI secrets) are transmitted verbatim to the attacker. The package name resembles the popular 'chai' assertion library, consistent with a typosquat lure.

Malicious versions

1 flagged

2.4.7

Indicators of compromise (SHA-256)

90d46bc75e0c086e929855baefd9f9f847ebe6e85f8a004c9de72502d0fb6263

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for chai-as-agile (version 2.4.7).
If you installed it — respond
chai-as-agile is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If chai-as-agile 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-agile on npm has been identified as a malicious package (version 2.4.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020079

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks chai-as-agile-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database