Advisory

MAL-2026-17772

Also known as: GHSA-rm73-xcfr-76qq

Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.

Summary

Malicious code in liferay-workspace-scripts (npm)

Details

---
_-= Per source details. Do not edit below this line.=-_

Source: amazon-inspector (3395e72ef77703732691fce21359206afea7598fb3d1dab29ded4b2e1c7cd28f)
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.

Source: ghsa-malware (6e51ac41e8208971e9eaa47cabead2ff84860b1f4c8f9ada9dea9ff4f642e80c)
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.

Severity

Not rated by the source.

Dates

Published
2026-10-11 13:58 UTC
Modified
2026-10-12 14:00 UTC

Affected packages and fixes

liferay-workspace-scripts

npm · All systems

Affected

  • introduced 0 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: OpenSSF Malicious Packages · Apache-2.0

Sources & licences