sigchain-js (npm) · Malicious Code
Affects sigchain-jsSource GCVE Database
Malicious package : remove sigchain-js and rotate any secrets on hosts that installed it.
Data as of 26 Oct 2026, 16:15 UTC
Malicious package
Published to npm · OSV MAL-2026-11146
What to do
Remove sigchain-js 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 |
|---|---|---|
| npmsigchain-js | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The npm package sigchain-js versions 1.0.0 and 1.0.1 contain malicious code in their published distribution bundles. These bundles include top-level code that decrypts an encrypted payload from companion packages and executes it via a spawned detached Node.js child process. This behavior enables arbitrary code execution on the host machine when the package is imported or required. The malicious payload is split across cooperating packages, including a dependency named thedata and a transitively included package tchain-api, which mimics an official SDK. Additionally, the package pins a non-existent axios version, redirecting installs to a squatted package. This threat does not have a known patch or fix at this time.