Which versions of capes-ui are malicious?

The following npm versions of capes-ui are flagged malicious: 10.0.7, 10.0.8. Treat any of these as compromised.

How do I remediate capes-ui if I installed it?

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

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

Yes — capes-ui is associated with the RLMA-2025-06079 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 capes-ui across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for capes-ui (2 malicious versions).

Malicious package

capes-uinpm

Advisory published Nov 9, 2025Updated Dec 23, 2025

capes-ui is a confirmed malicious npm package (MAL-2025-49400) that executes malicious code on install (malicious versions 10.0.7, 10.0.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in capes-ui (npm)

MAL-2025-49400

Immediate action

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

npm uninstall capes-ui

What this malware does

The package capes-ui was found to contain malicious code.

Malicious versions

2 flagged

10.0.710.0.8

Indicators of compromise (SHA-256)

8a6f39dd3b6ae0e4941ca23e3a41820dc7a088eeaaa0d56622174d29ae219f72

a650e5bd18d5c77aec6c6a920a0e30a648f58673867b1c5e031155e8bdc28285

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06079

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks capes-ui-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