Which versions of @emerald-react/icon are malicious?

The following npm versions of @emerald-react/icon are flagged malicious: 999.999.999, 9999.9999.9999. Treat any of these as compromised.

How do I remediate @emerald-react/icon if I installed it?

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

If @emerald-react/icon 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 @emerald-react/icon part of a known attack campaign?

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

Search your lockfiles and build artifacts for @emerald-react/icon (2 malicious versions).

Part of a larger attack: @emerald-react published 20 malicious packages. See the full campaign →

Malicious package

@emerald-react/iconnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

@emerald-react/icon is a confirmed malicious npm package (MAL-2026-1610) that executes malicious code on install (malicious versions 999.999.999, 9999.9999.9999). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @emerald-react/icon (npm)

MAL-2026-1610

Immediate action

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

npm uninstall @emerald-react/icon

What this malware does

The package @emerald-react/icon was found to contain malicious code.

Malicious versions

2 flagged

999.999.9999999.9999.9999

Indicators of compromise (SHA-256)

e81d2c4334c91e3126f85fbb2f586287b0e22af1ab4fb88c768b18bfaa7abe70

f4a73cc0869fbd6a9f90687210caf69cb8e9ee872202bc342c24c07ead3399b0

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-00992

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @emerald-react/icon-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