Which versions of chai-as-otc are malicious?

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

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

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

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

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

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

Malicious package

chai-as-otcnpm

Advisory published Aug 25, 2026Updated Aug 25, 2026

chai-as-otc is a confirmed malicious npm package (MAL-2026-14491) 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-otc (npm)

MAL-2026-14491

Immediate action

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

npm uninstall chai-as-otc

What this malware does

On module load, lib/initializeCaller.js (required from index.js) runs an IIFE that POSTs the full process.env to a base64-obfuscated endpoint decoding to https://ipcheck-hashed.vercel.app/api/auth/6c1d60d35852ef0c05df, then passes the HTTP response body to new Function("require", response.data) and invokes it with require, yielding arbitrary Node code execution on the installer's host at load time. The package is framed as a pino-style logging middleware with a 'Successfully synced!' cover string, but the actual behavior is a covert credential harvester and remote loader.

Malicious versions

1 flagged

1.0.5

Indicators of compromise (SHA-256)

cf771adc4f92ba0d79ea56bdcc1e42db57d1bc7421f0dadb0544f619e16b5ca1

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for chai-as-otc (version 1.0.5).
If you installed it — respond
chai-as-otc 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-otc 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-otc 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-018737

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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