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

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

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

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

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

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

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

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

Malicious package

@emerald-react/dropdownnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

MAL-2026-1608

Immediate action

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

npm uninstall @emerald-react/dropdown

What this malware does

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

Malicious versions

2 flagged

999.999.9999999.9999.9999

Indicators of compromise (SHA-256)

66523573cff2464686e9675a73d81c6293ea4724c5bc51e6e33f950ed87cbaec

b6123af9a9aaf14730582221f6fa6a266c56c772a01f82e3e4812aea90b691f1

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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