ts-webplug (npm) · Malicious Code
Affects ts-webplugSource GCVE Database
Malicious package : remove ts-webplug and rotate any secrets on hosts that installed it.
Data as of 11 Jul 2026, 09:43 UTC
Malicious package
Published to npm · OSV MAL-2026-5994
What to do
Remove ts-webplug 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-webplug | Affected
| 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 (a120eb8e3f6ca34493b7f282544523ab60137e8388148b191f46cda094e50789) The package impersonates the pino logger (README titled 'chai-mocks', badges linking to pinojs/pino, module export named `pino`) while its actual package name `ts-webplug` is unrelated. When a consumer requires the package and invokes its exported middleware, `index.js` spawns `lib/caller.js` as a detached Node child process. `lib/caller.js` performs `axios.get(...)` against https://jsonhosting.com/api/json/9343c2ce/raw, extracts the `cookie` field from the response, and passes it to `new Function.constructor('require', s)(require)` — evaluating attacker-controlled JavaScript with full `require` access in the consumer's Node process. The remote URL is additionally concealed in a spoofed `process.env` object where `DEV_API_KEY` is a base64 blob decoding to a jsonkeeper.com URL (a second mutable, anonymous-host pointer in `lib/const.js` decodes to https://jsonkeeper.com/b/4NAKK). The fetch host is a mutable anonymous paste service — today's payload can be swapped for anything at any time — and the executed code runs with full Node privileges on the installer/consumer machine. ## Source: ghsa-malware (ab49780fe41f3794685e5956a0d5a7c3ecdf35303b839d14f2b2d6c11d20032e) 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.