Which versions of adminui-deps are malicious?

The following npm versions of adminui-deps are flagged malicious: 1.0.0, 11.10.11. Treat any of these as compromised.

How do I remediate adminui-deps if I installed it?

Remove adminui-deps 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 adminui-deps — how do I know if it already compromised me?

If adminui-deps 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 adminui-deps part of a known attack campaign?

Yes — adminui-deps is associated with the RLMA-2026-04822, RLUA-2026-05959 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 adminui-deps across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for adminui-deps (2 malicious versions).

Malicious package

adminui-depsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

adminui-deps is a confirmed malicious npm package (MAL-2026-7106) that executes malicious code on install (malicious versions 1.0.0, 11.10.11). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in adminui-deps (npm)

MAL-2026-7106

Immediate action

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

npm uninstall adminui-deps

Malicious versions

2 flagged

1.0.011.10.11

Indicators of compromise (SHA-256)

c706b2aad6606436da3820ab1c6561e17e8c55d31f85a023d3bccdfb3d574df5

822326da5bbbe51a3003e378ac4132f1ed8a0cf7a6d3c4ed17544cf93af6cfd7

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for adminui-deps (2 malicious versions).
If you installed it — respond
Remove adminui-deps 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 adminui-deps 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. adminui-deps on npm has been identified as a malicious package (versions 1.0.0, 11.10.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04822RLUA-2026-05959

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks adminui-deps-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