depcruise-wrap-stream-in-htmlnpm
depcruise-wrap-stream-in-html is a confirmed malicious npm package (MAL-2026-14068) that typosquats a legitimate package to trick installs (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in depcruise-wrap-stream-in-html (npm)
What this malware does
[email protected] is a hollow package: index.js is module.exports = {} and the name mimics an internal helper of dependency-cruiser. Its only effect on install is resolving a runtime dependency ltidisafe from an arbitrary HTTPS tarball URL — https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.7.5.tgz — hosted on a Google Cloud Storage bucket unrelated to any known publisher of dependency-cruiser. On npm install, npm downloads and installs that tarball into node_modules, and any lifecycle scripts inside it execute on the installer's machine. The bucket owner can swap the tarball contents at any time without republishing to npm, bypassing registry scanning and version pinning guarantees. The 99.9.1 version number and lookalike name are consistent with a dependency-confusion / smuggling lure.
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 depcruise-wrap-stream-in-html (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging depcruise-wrap-stream-in-html across your stack and pipelines.
If you installed it — respond
depcruise-wrap-stream-in-html is a typosquat — you almost certainly intended a legitimately-named package. Remove depcruise-wrap-stream-in-html, 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 depcruise-wrap-stream-in-html 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 depcruise-wrap-stream-in-html 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 depcruise-wrap-stream-in-html-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.