MalwarePublished 8 Jul 2026Updated 10 Jul 2026

chai-redirection (npm) · Malicious Code

Affects chai-redirectionSource GCVE Database

Malicious package : remove chai-redirection and rotate any secrets on hosts that installed it.

Data as of 11 Jul 2026, 09:43 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-6995

What to do

Remove chai-redirection from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmchai-redirection	Affected =0.0.1 =0.0.4 =0.0.3	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (38236fbbdbbaa8f8ed9315c3a4ff01fbf049215896036b1cb68611681fe0eb00) chai-redirection presents itself as a chai assertion plugin but its main entry (index.js) unconditionally spawns a detached Node child process running lib/caller.js the moment the package is required. caller.js issues an HTTPS GET to https://www.jsonkeeper.com/b/PC5CK (a mutable pastebin-style host) and passes the response body's `cookie` field to `new Function('require', res.data.cookie)(require)`, executing attacker-controlled JavaScript in the installer's Node process with full `require` access. A secondary code path builds a URL from lib/config values, and on a 404 response whose body carries a `token` field, constructs `new Function.constructor('require', res.token)` and invokes it with `require` — a second remote-code-execution channel. The advertised chai plugin API (validJWT, safeString, etc.) is a cover story: the loader runs before any exports are used, so merely requiring this package as a chai plugin triggers remote code execution. The mutable pastebin source means today's payload can be replaced with anything at any time without republishing the package. ## Source: ghsa-malware (996d340e8231861ae21a30061eda3164b993e15bd08346375d8f886824b4fb6f) 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.

Impact

Any system that installs or runs the affected versions of chai-redirection is subject to immediate and full remote code execution by an attacker-controlled payload. This grants the attacker full control over the Node.js process environment, including access to require modules, enabling arbitrary code execution, data theft, and system compromise. Because the malicious code runs on package load, the risk exists even if the package's exported API is never used. The mutable external payload source means the attacker can update or change the malicious code at will, increasing the risk of ongoing compromise. Systems with this package should be considered fully compromised, and secrets or keys stored on them should be rotated from a trusted environment.

Defensive guidance

The recommended mitigation is to immediately remove all affected versions (=0.0.1, =0.0.3, =0.0.4) of the chai-redirection package from all systems. Because the package executes attacker-controlled code with full privileges, any system that had this package installed or running should be treated as fully compromised. All secrets, credentials, and keys stored on the system should be rotated from a different, trusted machine. Additional forensic analysis and remediation may be necessary to ensure complete removal of any malicious artifacts. Monitor vendor advisories for any future updates or official fixes.

Summary

The chai-redirection npm package masquerades as a chai assertion plugin but contains embedded malicious code that triggers remote code execution immediately upon being required. Its main entry point spawns a detached Node child process that performs an HTTPS GET request to a mutable pastebin-style URL, retrieving JavaScript code from the response's 'cookie' field and executing it with full Node.js require privileges. A secondary code path fetches a token from a configurable URL and executes it similarly, providing a second remote code execution vector. Because the malicious code runs before any exports are accessed, simply requiring the package triggers execution of attacker-controlled code. The mutable external source allows the attacker to change the payload at any time without republishing the package, making the threat dynamic and persistent. This behavior effectively compromises any system that installs or runs this package.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Jul 2026, 09:29 UTC

Technical details

References

Community reviews