# MAL-2026-18291: Malicious code in sc-hydrate-carousel-price (npm)


- **Type:** Malicious package
- **Package:** `sc-hydrate-carousel-price` (npm)
- **Published:** 25 Oct 2026
- **Also known as:** GHSA-9gcx-88qx-rxch

## What is MAL-2026-18291?

MAL-2026-18291 is a malicious package in sc-hydrate-carousel-price, published on 25 Oct 2026. 

### Official description

package.json declares a dependency `ltidisafe` whose source is a bare HTTPS tarball URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-4.0.3.tgz) rather than a registry version range. On npm install, npm fetches whatever bytes are served at that URL and installs them, running any lifecycle scripts contained in the fetched tarball. There is no version pin, no integrity hash, and no signature check, so the contents are mutable and controlled by whoever controls that storage bucket. The package's own shipped code is an inert stub (index.js is `module.exports = {};`), so the manifest line is effectively the entire delivered payload — the published package functions as a loader for externally hosted code. The implausibly high version (99.9.1) combined with the `sc-hydrate-carousel-price` name is consistent with a dependency-confusion shape intended to win resolution against an internal package.

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-18291?

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-18291 is a malicious package: sc-hydrate-carousel-price (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-18291/ (Markdown: https://insights.sbomify.com/MAL-2026-18291/index.md)
```

## Sources

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

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