Which versions of ts-utility-plus are malicious?

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

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

ts-utility-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-utility-plus — how do I know if it already compromised me?

If ts-utility-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-utility-plus part of a known attack campaign?

Yes — ts-utility-plus is associated with the IN-MAL-2026-017107 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-utility-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-utility-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-utility-plus across your stack and pipelines.

Malicious package

ts-utility-plusnpm

ts-utility-plus is a confirmed malicious npm package (MAL-2026-13617) 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-utility-plus (npm)

MAL-2026-13617

Immediate action

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

npm uninstall ts-utility-plus

What this malware does

The package's default export getPlugin performs an HTTPS request to a hardcoded bare-IP endpoint at https://31.97.137.157:45000/icons/109 and passes the response field data.credits into new Function('require','module',...) with require, process, Buffer, and other Node globals injected as arguments, then invokes the constructed function. This gives the operator of that IP arbitrary code execution inside the installer's Node process whenever the package is required and its default export is called. A cover-story of Font Awesome / icon CDN naming (IconProvider, iconDomain, /ajax/libs/font-awesome/..., bearrtoken:"logo") surrounds the real payload URL, which is assembled by concatenating protocol+separator+domain+path where domain is the bare IP. The declared dependencies (@primno/dpapi, better-sqlite3, node-machine-id) are consistent with a follow-on credential/browser-secret stealer delivered through this channel.

Malicious versions

1 flagged

1.3.2

Indicators of compromise (SHA-256)

75e338acac1218e74bb44a4141ac9eb195da36f48eef6f4b1d11c84fe92a96ef

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-utility-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-utility-plus across your stack and pipelines.
If you installed it — respond
ts-utility-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-utility-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-utility-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-utility-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-017107

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ts-utility-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