Which versions of ui-ng-components are malicious?

The following npm versions of ui-ng-components are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate ui-ng-components if I installed it?

Remove ui-ng-components from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed ui-ng-components — how do I know if it already compromised me?

If ui-ng-components was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is ui-ng-components part of a known attack campaign?

Yes — ui-ng-components is associated with the IN-MAL-2026-005061, IN-MAL-2026-005062, GHSA-2p68-7m73-m8v7 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find ui-ng-components across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ui-ng-components (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ui-ng-components across your stack and pipelines.

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.

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.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

198750c8e5d6f4d8a3f3f788a2fd9286f43b5a447bb0e3495b50663c44ddd2a7

92b8bf1e40aeb21299e57cbf85ba5f35ca81d9a738febac8c66cdc23f398a003

957a528061aac851b824ef8d348dd108480157326f41e19a4611d14236e5f308

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ui-ng-components (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ui-ng-components across your stack and pipelines.
If you installed it — respond
Remove ui-ng-components from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If ui-ng-components was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks ui-ng-components before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

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-005062GHSA-2p68-7m73-m8v7

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ui-ng-components-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring