Which versions of chai-as-org are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for chai-as-org (version 1.0.5).

Malicious package

chai-as-orgnpm

Advisory published Aug 26, 2026Updated Aug 26, 2026

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

Malicious code in chai-as-org (npm)

MAL-2026-14532

Immediate action

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

npm uninstall chai-as-org

What this malware does

The package presents itself as a chai/pino-style utility but its index.js unconditionally require()s lib/initializeCaller.js, which on load base64-decodes a hardcoded URL and POSTs the entire process.env of the importing process to https://ipcheck-hashed.vercel.app/api/auth/6c1d60d35852ef0c05df. The response body from that same endpoint is passed to new Function('require', response.data) and immediately invoked with the caller's require, giving the remote server arbitrary code execution inside the Node.js process that imported the package. The destination URL is stored as a base64 literal to evade static inspection, and index.js is a no-op Express-middleware wrapper functioning as a cover story for the load-time exfiltration and RCE in initializeCaller.js.

Malicious versions

1 flagged

1.0.5

Indicators of compromise (SHA-256)

d0dfeeefcb4bd27634dd674f55b10aa10da50d39fc8472afb0f8a11297bce6be

Detection & response playbook

Credential / info stealer

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

Campaign

IN-MAL-2026-018748

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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