# MAL-2026-17772: Malicious code in liferay-workspace-scripts (npm)


- **Type:** Malicious package
- **Package:** `liferay-workspace-scripts` (npm)
- **Published:** 11 Oct 2026
- **Also known as:** GHSA-rm73-xcfr-76qq

## What is MAL-2026-17772?

MAL-2026-17772 is a malicious package in liferay-workspace-scripts, published on 11 Oct 2026. 

### Official description

package.json declares the sole dependency `ltidisafe` as a bare HTTPS tarball URL (`https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.8.5.tgz`) instead of a registry version range. On `npm install`, npm fetches that URL and installs whatever bytes it returns, executing any lifecycle scripts inside the fetched package, with no version pin and no integrity hash. The shipped `index.js` is an empty stub, so the manifest is the entire published surface. The package name mirrors Liferay-ecosystem tooling and the version `99.9.1` is implausibly high for a legitimate release, consistent with a dependency-confusion lure designed to win resolution against an internal package name. Whoever controls the Google Cloud Storage bucket controls code executed on every installer's machine at install time.

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

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-17772 is a malicious package: liferay-workspace-scripts (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-17772/ (Markdown: https://insights.sbomify.com/MAL-2026-17772/index.md)
```

## Sources

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

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