Which versions of ict-ui-carbon are malicious?

The following npm versions of ict-ui-carbon are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate ict-ui-carbon if I installed it?

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

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

Yes — ict-ui-carbon is associated with the RLMA-2026-05114, RLUA-2026-06281 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 ict-ui-carbon across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ict-ui-carbon (version 99.99.99).

Malicious package

ict-ui-carbonnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

ict-ui-carbon is a confirmed malicious npm package (MAL-2026-7300) that executes malicious code on install (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ict-ui-carbon (npm)

MAL-2026-7300

Immediate action

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

npm uninstall ict-ui-carbon

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

18ac6702aea3a088861150d730e453031a53865d3c17ec31d33e819fd7072145

1a3845ed4d472bba8feb7b86dd5e8bd22879bc718da5e53392d6500311d08a60

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05114RLUA-2026-06281

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks ict-ui-carbon-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