Which versions of chai-as-tokenized are malicious?

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

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

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

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

Yes — chai-as-tokenized is associated with the IN-MAL-2026-006793, GHSA-4hvx-q2w4-f48v 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-tokenized 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-tokenized (version 7.2.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-as-tokenized across your stack and pipelines.

Malicious package

chai-as-tokenizednpm

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

Malicious code in chai-as-tokenized (npm)

MAL-2026-5902

Immediate action

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

npm uninstall chai-as-tokenized

What this malware does

Package name impersonates chai-as-promised, and the README is a copy of pino's documentation, but the actual code is a remote-code-execution dropper. The exported middleware (advertised as chai.use(chaiAsTokenized)) spawns lib/initializeCaller.js as a detached node child with stdio:'ignore' and child.unref(), hiding output and surviving parent exit. The child shadows the process global with a fake object whose env values are base64 strings, atob-decodes them to obtain https://amethyst-lorrin-26.tiiny.site/index.json and the header x-secret-key: _, fetches JSON from that anonymous tiiny.site endpoint, and passes the response's cookie field to new Function.constructor('require', response) invoked with the live require — granting the remote, attacker-controlled host arbitrary code execution inside the consuming process with full module access. Combined signals: name-impersonation of a popular chai plugin, README mismatch with shipped code, base64-obfuscated C2 URL, anonymous static-file host (not a publisher domain), detached-and-silenced child spawn, and remote response evaluated as JavaScript.

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

7.2.3

Indicators of compromise (SHA-256)

55c10da182a0c79ca5eb0f85c6b2e334b7ee4e90946dfcc34feb44e80afa4485

fe8e4af381c4b8eb3ff6a93cbd50f27cd0196c86038024c04ad803780f72cae9

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chai-as-tokenized (version 7.2.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chai-as-tokenized across your stack and pipelines.
If you installed it — respond
chai-as-tokenized 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-tokenized 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-tokenized 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-tokenized on npm has been identified as a malicious package (version 7.2.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006793GHSA-4hvx-q2w4-f48v

References

Credits

Amazon Inspector · finder

Detect & block this

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