Which versions of ts-toolkit-plus are malicious?

The following npm versions of ts-toolkit-plus are flagged malicious: 1.3.2. Treat any of these as compromised.

How do I remediate ts-toolkit-plus if I installed it?

ts-toolkit-plus is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed ts-toolkit-plus — how do I know if it already compromised me?

If ts-toolkit-plus 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.

Is ts-toolkit-plus part of a known attack campaign?

Yes — ts-toolkit-plus is associated with the IN-MAL-2026-014940, GHSA-99wx-749q-58xh campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find ts-toolkit-plus across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ts-toolkit-plus (version 1.3.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ts-toolkit-plus across your stack and pipelines.

Malicious package

ts-toolkit-plusnpm

ts-toolkit-plus is a confirmed malicious npm package (MAL-2026-12812) that steals credentials and exfiltrates sensitive data (malicious version 1.3.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ts-toolkit-plus (npm)

MAL-2026-12812

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall ts-toolkit-plus

What this malware does

The package's main entry defines a getPlugin() function that performs an HTTPS request to a hardcoded bare-IP endpoint at 31.97.137.157:45000/icons/112 and passes the response field data.credits to new Function('require','module',...,'Promise', data.credits), executing whatever the remote host returns with full Node.js context including require, process, Buffer, and globalThis. The destination URL is assembled from split protocol/separator/domain/path fragments and wrapped in benign 'icon/CDN' naming that hides the code-execution sink. The declared dependencies (@primno/dpapi for Windows DPAPI unwrap of browser-stored secrets, node-machine-id for host fingerprinting, better-sqlite3/sqlite3 for browser profile databases, socket.io-client) do not correspond to the advertised 'crypto checkout' purpose and pre-stage tooling a remote payload can invoke via the injected require() to harvest Windows browser credentials and cookies. Any consumer that require/imports this package and reaches the getPlugin path grants the remote operator arbitrary code execution on the installer's 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

1 flagged

1.3.2

Indicators of compromise (SHA-256)

49d47be3f5dc16ea70755e0233f46106d3f50d1d5384a4f20c76b91463c9876c

cad454e0e312c87020333f7ece00363eb627c8b1b1334431c662c09a6af7dad1

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ts-toolkit-plus (version 1.3.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ts-toolkit-plus across your stack and pipelines.
If you installed it — respond
ts-toolkit-plus is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If ts-toolkit-plus 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-toolkit-plus 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

No. ts-toolkit-plus on npm has been identified as a malicious package (version 1.3.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014940GHSA-99wx-749q-58xh

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ts-toolkit-plus-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database