# MAL-2026-14068: Malicious code in depcruise-wrap-stream-in-html (npm)


- **Type:** Malicious package
- **Package:** `depcruise-wrap-stream-in-html` (npm)
- **Published:** 15 Aug 2026
- **Also known as:** GHSA-fr93-j26p-9j5f

## What is MAL-2026-14068?

MAL-2026-14068 is a malicious package in depcruise-wrap-stream-in-html, published on 15 Aug 2026. 

### Official description

depcruise-wrap-stream-in-html@99.9.1 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.

## What should I do about MAL-2026-14068?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-14068 is a malicious package: depcruise-wrap-stream-in-html (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-14068/ (Markdown: https://insights.sbomify.com/MAL-2026-14068/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-14068

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-14068/
Summaries are generated and may contain mistakes; the official description above is the record.