Which versions of chai-as-vite are malicious?

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

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

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

If chai-as-vite was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is chai-as-vite part of a known attack campaign?

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

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chai-as-vite (version 2.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-as-vite across your stack and pipelines.

Malicious package

chai-as-vitenpm

Malicious code in chai-as-vite (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4514

Immediate action

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

npm uninstall chai-as-vite

What this malware does

The package masquerades as a pino-style logger (exports module.exports.pino = middleware, keywords fast,logger,stream,json, lib filenames proto.js, redaction.js, multistream.js, transport.js) under a name evoking chai/vite tooling. When a consumer requires the package and invokes the exported middleware, lib/initializeCaller.js is launched as a detached node child process. That script defines a local process shadow whose env holds base64 strings (DEV_API_KEY, DEV_SECRET_KEY, DEV_SECRET_VALUE), atob-decodes them to recover the URL https://purple-kelila-79.tiiny.site/data.json and the header x-secret-key: _, fetches the response via axios, then executes the response body with new Function.constructor('require', response)(require) — full arbitrary code execution with require access on the installer's machine, with retry. The destination is an anonymous, mutable tiiny.site host with no version pinning and no integrity check, so the operator can rotate the delivered payload at will. Base64-encoded URL and header values, the fake process.env shadow, and the detached child-process launch are intentional evasion.

Malicious versions

1 flagged

2.3.5

Indicators of compromise (SHA-256)

b7096b7b983ae63f8e59f9e047440547c9536f6c4c9da0ac46909b91a9d4e10e

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chai-as-vite (version 2.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-as-vite across your stack and pipelines.
If you installed it — respond
Remove chai-as-vite 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-as-vite was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks chai-as-vite before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. chai-as-vite on npm has been identified as a malicious package (version 2.3.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-003997

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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