# MAL-2026-4827: Malicious code in unleash-js (npm)


- **Type:** Malicious package
- **Package:** `unleash-js` (npm)
- **Published:** 26 May 2026
- **Also known as:** GHSA-j5f8-3p7p-5c4c

## What is MAL-2026-4827?

MAL-2026-4827 is a malicious package in unleash-js, published on 26 May 2026. 

### Official description

unleash-js@99.9.1 is an empty stub package (index.js exports `{}`, 35 bytes; no author, no description) whose sole effect is to pull a chained dependency `ltidisafe` from an arbitrary tarball URL on a third-party Google Cloud Storage bucket: `https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.7.7.tgz`. The host is not the package publisher's domain, the tarball is unpinned by hash, and the bucket is mutable — any installer running `npm install unleash-js` will fetch and execute whatever bytes currently sit at that URL, including any lifecycle scripts (preinstall/install/postinstall) inside the fetched tarball. The 99.9.1 version, empty metadata, and `depenconf` path segment are consistent with a dependency-confusion squat targeting an internal package name; the stub's only purpose is to act as a loader for the externally hosted payload.

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 'unleash-js' @ 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-4827?

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

## Sources

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

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