# MAL-2026-5454: Malicious code in ui-ng-components (npm)


- **Type:** Malicious package
- **Package:** `ui-ng-components` (npm)
- **Published:** 9 Jun 2026
- **Also known as:** GHSA-2p68-7m73-m8v7

## What is MAL-2026-5454?

MAL-2026-5454 is a malicious package in ui-ng-components, published on 9 Jun 2026. 

### Official description

Package ui-ng-components@99.9.1 is an empty shell (index.js exports `{}`, no author, no description, no functionality) with a single dependency declared as a remote tarball URL: `https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.7.9.tgz`. The version number 99.9.1 and the literal `depenconf` segment in the dependency URL are the canonical fingerprint of a dependency-confusion override targeting an internal Angular UI component name. On `npm install`, npm fetches and installs that opaque tarball as a transitive dependency; any lifecycle scripts inside it run on the installer's machine, and its contents are not reviewable from the registry. The host package ships no library code — its only on-install effect is dropping in this externally-hosted tarball, making the install itself the attack surface.

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

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-5454 is a malicious package: ui-ng-components (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-5454/ (Markdown: https://insights.sbomify.com/MAL-2026-5454/index.md)
```

## Sources

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

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