# MAL-2026-17566: Malicious code in unified-platform (npm)


- **Type:** Malicious package
- **Package:** `unified-platform` (npm)
- **Published:** 5 Oct 2026
- **Also known as:** GHSA-9j7c-8j8v-428c

## What is MAL-2026-17566?

MAL-2026-17566 is a malicious package in unified-platform, published on 5 Oct 2026. 

### Official description

package.json declares a single dependency 'ltidisafe' sourced directly from the off-registry URL https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.8.2.tgz, with no registry version range and no integrity hash. On npm install, npm fetches and installs whatever bytes that URL currently serves, executing any lifecycle scripts contained inside the fetched tarball under the installer's account. The GCS bucket host is not tied to any declared publisher of this package, and the fetched content can be changed at any time without a corresponding package republish. The shipped index.js is an empty stub, so the manifest's off-registry fetch is the package's entire effect on the installer. The package name 'unified-platform' at the implausibly high version 99.9.1 is consistent with a dependency-confusion lure targeting an internal name.

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

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

## Sources

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

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