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

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

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

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

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

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

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

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

Malicious package

@emerald-react/bannernpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

@emerald-react/banner is a confirmed malicious npm package (MAL-2026-1600) 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/banner (npm)

MAL-2026-1600

Immediate action

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

npm uninstall @emerald-react/banner

What this malware does

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

Malicious versions

2 flagged

999.999.9999999.9999.9999

Indicators of compromise (SHA-256)

1b783af9afd3b94addf607ec4609784f99019397bf8b366192d204c3979b4630

9a79719d2b89120a3c7d4f82af0ddf795ed28d6300ec3eb9e46003aead94c2fb

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @emerald-react/banner (2 malicious versions).
If you installed it — respond
Remove @emerald-react/banner 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/banner 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/banner 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-00982

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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