Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

ui-ng-componentsnpm

Malicious code in ui-ng-components (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5454
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall ui-ng-components

What this malware does

Package [email protected] 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.

Malicious versions

1 flagged
99.9.1

Indicators of compromise (SHA-256)

198750c8e5d6f4d8a3f3f788a2fd9286f43b5a447bb0e3495b50663c44ddd2a7
92b8bf1e40aeb21299e57cbf85ba5f35ca81d9a738febac8c66cdc23f398a003

Frequently asked questions

No. ui-ng-components on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005061IN-MAL-2026-005062

References

Credits

  • Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection
ui-ng-components (npm) malicious package — MAL-2026-5454 | O3 Security