Which versions of net-util-y8 are malicious?

The following npm versions of net-util-y8 are flagged malicious: 1.1788432509.0. Treat any of these as compromised.

How do I remediate net-util-y8 if I installed it?

net-util-y8 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 net-util-y8 — how do I know if it already compromised me?

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

Yes — net-util-y8 is associated with the IN-MAL-2026-019458 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 net-util-y8 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 net-util-y8 (version 1.1788432509.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging net-util-y8 across your stack and pipelines.

Malicious package

net-util-y8npm

net-util-y8 is a confirmed malicious npm package (MAL-2026-15901) that steals credentials and exfiltrates sensitive data (malicious version 1.1788432509.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in net-util-y8 (npm)

MAL-2026-15901

Immediate action

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

npm uninstall net-util-y8

What this malware does

The package has no real functionality: index.js contains only an empty comment and package.json declares no exports or lifecycle scripts. The description field in package.json is a ~56KB base64 blob that decodes to a ~42KB POSIX shell script implementing an XMRig Monero miner dropper. The decoded script preflights curl/wget/openssl and perl (installing them via the system package manager with root privileges if missing), fetches XMRig binaries from gitlab.com/albertotrindade131/al and a ghfast.top proxy in front of github.com/lucas77335/xmrig-amd releases, points the miner at the pool xmr.kryptex.network:8029 with a hardcoded Monero wallet address (883kAB7Ufo...gBCFH), and includes routines to kill competing miners and mask its process name. The script also references a sibling package net-util-x7 and a registry-latest lookup at registry.npmjs.org/cbc97b7a/latest, indicating this is a staging component of a multi-package cryptomining campaign. Encoding an executable payload inside the manifest description field is a smuggling technique to keep the payload off code-scanning paths while still shipping it in the published tarball.

Malicious versions

1 flagged

1.1788432509.0

Indicators of compromise (SHA-256)

d1e81ce327647324756e0ea15d1016d45cd5bb092dd0099418ba2db59eca98a7

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 net-util-y8 (version 1.1788432509.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging net-util-y8 across your stack and pipelines.
If you installed it — respond
net-util-y8 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 net-util-y8 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 net-util-y8 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. net-util-y8 on npm has been identified as a malicious package (version 1.1788432509.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019458

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks net-util-y8-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