# MAL-2026-14053: Malicious code in depcruise-baseline (npm)


- **Type:** Malicious package
- **Package:** `depcruise-baseline` (npm)
- **Published:** 15 Aug 2026
- **Also known as:** GHSA-rgcp-8955-2r93

## What is MAL-2026-14053?

MAL-2026-14053 is a malicious package in depcruise-baseline, published on 15 Aug 2026. 

### Official description

depcruise-baseline@99.9.1 has a name resembling dependency-cruiser/depcruise but ships an empty index.js and declares its sole runtime dependency as a direct https:// tarball URL rather than a registry package: "ltidisafe": "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.7.4.tgz". On npm install, npm downloads and installs that tarball as a transitive dependency, so whoever controls the ltidi.storage.googleapis.com bucket controls arbitrary code that runs on the installer via that dependency's require graph and lifecycle hooks. The package has no functional code of its own; its only effect is to pull code from an author-controlled, out-of-registry location into the installer's dependency tree.

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.

The OpenSSF Package Analysis project identified 'depcruise-baseline' @ 99.9.1 (npm) as malicious.

It is considered malicious because:

- The package communicates with a domain associated with malicious activity.

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

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-14053 is a malicious package: depcruise-baseline (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-14053/ (Markdown: https://insights.sbomify.com/MAL-2026-14053/index.md)
```

## Sources

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

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