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

warp-drive-internal-toolingnpm

warp-drive-internal-tooling is a confirmed malicious npm package (MAL-2026-12500) that executes malicious code on install (malicious version 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in warp-drive-internal-tooling (npm)

MAL-2026-12500
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall warp-drive-internal-tooling

What this malware does

[email protected] declares a preinstall hook that runs index.js, which on Windows spawns a hidden-window PowerShell process (powershell -WindowStyle Hidden) that downloads a zip archive from the anonymous file host files.catbox.moe (https://files.catbox.moe/5khq55.zip), extracts it into %TEMP%, and launches Verification_Tool.exe via Start-Process. The remote host is an unauthenticated throwaway file service unrelated to the package's stated purpose, the download is unpinned and unverified (no hash, no signature), and the fetched binary is opaque. Because npm auto-runs preinstall on every npm install, this results in unattended execution of an attacker-controlled Windows executable on the installer's machine, with concealment (hidden PowerShell window, staging under %TEMP% with a benign 'Verification_Tool' filename) consistent with a dropper rather than a legitimate build step.

Malicious versions

1 flagged
99.9.9

Indicators of compromise (SHA-256)

a62165101225b7ad5371e9310e013a9e1dc69b59a475a7a4ccd7cdf0d7996c1d

Detection & response playbook

Malicious package

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for warp-drive-internal-tooling (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 warp-drive-internal-tooling across your stack and pipelines.

  2. If you installed it — respond

    Remove warp-drive-internal-tooling 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.

  3. Did it already run?

    If warp-drive-internal-tooling 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 warp-drive-internal-tooling 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. warp-drive-internal-tooling 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-014648

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks warp-drive-internal-tooling-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
warp-drive-internal-tooling (npm) malicious package — MAL-2026-12500 | O3 Security