Which versions of chai-as-vec are malicious?

The following npm versions of chai-as-vec are flagged malicious: 2.3.5, 2.3.6, 2.3.7. Treat any of these as compromised.

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

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

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

Yes — chai-as-vec is associated with the GHSA-g2hx-wqmp-2fhg, RLMA-2026-05003, RLUA-2026-05509 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-vec 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-vec (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-as-vec across your stack and pipelines.

Malicious package

chai-as-vecnpm

chai-as-vec is a confirmed malicious npm package (MAL-2026-4168) that executes malicious code on install (malicious versions 2.3.5, 2.3.6, 2.3.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chai-as-vec (npm)

MAL-2026-4168

Immediate action

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

npm uninstall chai-as-vec

What this malware does

The package chai-as-vec was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

3 flagged

2.3.52.3.62.3.7

Indicators of compromise (SHA-256)

881a1aaf4a8b84da34d86f9eae83889cf848ee573bc5b1b0323a75edf9789e86

dc2944243ad1e093008da195dce566e63cce55ebe7fe0f5eb98ad71ffaddb81d

f5b998b5a6810821f030ec3d37b1112876e8c5d8937066a7df6fbbf689e2e514

01aee37cd7fc22152b31a19fb241c2bbc7ea5695845a36d11f491e6701083933

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-vec (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-as-vec across your stack and pipelines.
If you installed it — respond
Remove chai-as-vec 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-vec 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-vec 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-vec on npm has been identified as a malicious package (versions 2.3.5, 2.3.6, 2.3.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-g2hx-wqmp-2fhgRLMA-2026-05003RLUA-2026-05509

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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