ts-webplugnpm
ts-webplug is a confirmed malicious npm package (MAL-2026-5994) that opens a backdoor for remote access (malicious versions 3.0.5, 3.0.6, 3.0.7…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ts-webplug (npm)
What this malware does
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.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ts-webplug (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ts-webplug across your stack and pipelines.
If you installed it — respond
ts-webplug establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If ts-webplug 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 ts-webplug 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks ts-webplug-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.