Which versions of chai-uuids are malicious?

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

How do I remediate chai-uuids if I installed it?

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

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

Yes — chai-uuids is associated with the GHSA-9gvh-rg3c-5gr6, RLMA-2026-01199 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-uuids 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-uuids (version 2.3.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-uuids across your stack and pipelines.

Malicious package

chai-uuidsnpm

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

MAL-2025-192383

Immediate action

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

npm uninstall chai-uuids

What this malware does

The package chai-uuids 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

1 flagged

2.3.7

Indicators of compromise (SHA-256)

35cdb6e3e91aabd46ed85adb22b6972f688ae93b61f82f3cb8e2adb8f4294c48

42324f1af790a75f6b7a0e081a7d97f1e299d3d3c8c815e37c594d0835ced4a6

a1f528cfc493aa349b636c76797469df38429ca895ffcb0e9725a8217cd27703

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

Campaign

GHSA-9gvh-rg3c-5gr6RLMA-2026-01199

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks chai-uuids-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