utility-kit-tsnpm
Advisory published Updated
utility-kit-ts is a confirmed malicious npm package (MAL-2026-12493) 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 utility-kit-ts (npm)
What this malware does
The package's default export getPlugin issues a fetch to the hardcoded bare-IP URL https://31.97.137.157:45000/icons/109 and passes the returned data.credits field to the Function constructor, then invokes the compiled function with require, module, process, Buffer and other Node primitives bound in. Any code the remote host returns executes in the caller's Node.js process with full library privileges. A separate function setDefaultModule constructs a plausible cdnjs/font-awesome URL from an icon-domain map but is never called from any export, serving as decoy alongside the actual bare-IP eval sink. The package is advertised in its README as a zero-dependency TypeScript utility toolkit, but package.json declares dependencies (@primno/dpapi for Windows DPAPI unwrap, better-sqlite3, node-machine-id, socket.io-client, request) that are inconsistent with utility helpers and are pre-staged for the fetched payload to require — the building blocks of a credential/browser-cookie stealer.
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
Credential / info stealerFind it
Search your lockfiles and build artifacts for utility-kit-ts (version 1.3.2).
If you installed it — respond
utility-kit-ts 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 utility-kit-ts was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks utility-kit-ts-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.