Which versions of utility-kit-ts are malicious?

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

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

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.

I already installed utility-kit-ts — how do I know if it already compromised me?

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

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

Malicious package

utility-kit-tsnpm

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)

MAL-2026-12493

Immediate action

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

npm uninstall utility-kit-ts

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.

Malicious versions

1 flagged

1.3.2

Indicators of compromise (SHA-256)

11d4f4654f1acbc26d30e2ea0cae4816bf6e3a847dce2456134d050a38a8a575

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 utility-kit-ts (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 utility-kit-ts across your stack and pipelines.
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 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 utility-kit-ts 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. utility-kit-ts 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-014641

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database