ts-opus (npm) · Malicious Code
Affects ts-opusSource GCVE Database
Malicious package : remove ts-opus and rotate any secrets on hosts that installed it.
Data as of 26 Jun 2026, 22:35 UTC
Malicious package
Published to npm · OSV MAL-2026-6468
What to do
Remove ts-opus 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 |
|---|---|---|
| npmts-opus | 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 ts-opus npm package version 0.0.8 contains malicious code that injects a require call to an undeclared external module 'node-slot' inside files mimicking the legitimate big.js library. This causes execution of potentially arbitrary code from an external source at require-time, with all errors silently suppressed. This is a supply-chain attack targeting consumers expecting the genuine big.js package. Any system with this package installed should be considered fully compromised, and secrets should be rotated immediately.