Which versions of @egencia/uitk-react are malicious?

The following npm versions of @egencia/uitk-react are flagged malicious: 99.99.9. Treat any of these as compromised.

How do I remediate @egencia/uitk-react if I installed it?

Remove @egencia/uitk-react 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 @egencia/uitk-react — how do I know if it already compromised me?

If @egencia/uitk-react was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @egencia/uitk-react part of a known attack campaign?

Yes — @egencia/uitk-react is associated with the RLMA-2026-10628 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 @egencia/uitk-react across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @egencia/uitk-react (version 99.99.9).

Part of a larger attack: @egencia published 8 malicious packages. See the full campaign →

Malicious package

@egencia/uitk-reactnpm

Advisory published Sep 22, 2026Updated Sep 24, 2026

@egencia/uitk-react is a confirmed malicious npm package (MAL-2026-16518) that executes malicious code on install (malicious version 99.99.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @egencia/uitk-react (npm)

MAL-2026-16518

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @egencia/uitk-react

Malicious versions

1 flagged

99.99.9

Indicators of compromise (SHA-256)

1d463529f1eeb3310a01153fce1cbfd2665cb4bd06611ddee2b058d5d5136bdd

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @egencia/uitk-react (version 99.99.9).
If you installed it — respond
Remove @egencia/uitk-react 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 @egencia/uitk-react was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @egencia/uitk-react on npm has been identified as a malicious package (version 99.99.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-10628

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @egencia/uitk-react-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

Explore

All malware advisories How O3 detects malware Vulnerability database