Which versions of loadutils are malicious?

The following npm versions of loadutils are flagged malicious: 1.0.4, 1.0.5, 1.0.6. Treat any of these as compromised.

How do I remediate loadutils if I installed it?

loadutils is a typosquat — you almost certainly intended a legitimately-named package. Remove loadutils, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed loadutils — how do I know if it already compromised me?

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

Yes — loadutils is associated with the IN-MAL-2026-007768, IN-MAL-2026-008947, IN-MAL-2026-008953 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 loadutils 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 loadutils (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging loadutils across your stack and pipelines.

Malicious package

loadutilsnpm

loadutils is a confirmed malicious npm package (MAL-2026-6580) that typosquats a legitimate package to trick installs (malicious versions 1.0.4, 1.0.5, 1.0.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in loadutils (npm)

MAL-2026-6580

Immediate action

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

npm uninstall loadutils

What this malware does

Package loadutils is a typosquat of the widely-used webpack helper loader-utils. The shipped README documents the loader-utils API (urlToRequest, interpolateName, getHashDigest), but src/index.js instead exports a debug-style logger — name, documentation, and implementation do not align. On import, src/index.js executes require('debug-glitzs') at the top level, but debug-glitzs is not declared in dependencies, peerDependencies, or optionalDependencies; whatever resolves to that name in the installer's tree runs in the Node.js process as soon as loadutils is required. package.json additionally declares lessload@^1.0.1 as a runtime dependency that is never referenced in src/ and is unrelated to either the logger code or the advertised loader-utils API, pulling further unaccounted code into the installer's dependency tree on npm install. The contributors metadata also impersonates a well-known maintainer (Kiko Beats paired with an unrelated homepage alphacointech1010.com), reinforcing the deceptive packaging.

Malicious versions

3 flagged

1.0.41.0.51.0.6

Indicators of compromise (SHA-256)

31f1f1f6292d782062f6fff1f7422d9f1dc0eb1572e4372d6c0d574ccea3ab3a

f805ddc44a4e097758f4e952121d28a13cb3c6ea4425ac905118a3f9c4c171e0

fb0020bde7b301c12f88086e900a314ef7846d52d91e291f447b10b9a139e6b5

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for loadutils (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging loadutils across your stack and pipelines.
If you installed it — respond
loadutils is a typosquat — you almost certainly intended a legitimately-named package. Remove loadutils, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If loadutils 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 loadutils 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. loadutils on npm has been identified as a malicious package (versions 1.0.4, 1.0.5, 1.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007768IN-MAL-2026-008947IN-MAL-2026-008953

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks loadutils-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