Which versions of util-foriepft are malicious?

The following npm versions of util-foriepft are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate util-foriepft if I installed it?

Remove util-foriepft from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed util-foriepft — how do I know if it already compromised me?

If util-foriepft 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.

How do I find util-foriepft across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for util-foriepft (version 1.0.0).

Malicious package

util-foriepftnpm

Advisory published Oct 11, 2026Updated Oct 15, 2026

util-foriepft is a confirmed malicious npm package (MAL-2026-17878) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in util-foriepft (npm)

MAL-2026-17878

Immediate action

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

npm uninstall util-foriepft

What this malware does

[email protected] was published to npm on 2026-10-08 17:34 UTC by user regex33-hackerone. It is described as utility helpers but ships no library code: index.js is an empty module. thunderboltRegistry.js runs when the package is loaded, executes host commands through child_process and sends their output to a remote collector at dxpoc[.]gt[.]tc, and registry-manifest.min.json names Wix-internal modules (dependency confusion). Apart from the collector URL, thunderboltRegistry.js is byte-identical to the payload of [email protected] (MAL-2026-17705), published from the same account. The package was still available on 2026-10-11.

Malicious versions

1 flagged

1.0.0

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for util-foriepft (version 1.0.0).
If you installed it — respond
Remove util-foriepft from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If util-foriepft 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

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

References

osv.dev

Credits

Eunsoo Kim · finder

Detect & block this

O3 blocks util-foriepft-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database