Which versions of yahoo-commerce are malicious?

The following npm versions of yahoo-commerce are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate yahoo-commerce if I installed it?

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

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

Yes — yahoo-commerce is associated with the RLMA-2026-01662 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 yahoo-commerce across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for yahoo-commerce (version 99.99.99).

Malicious package

yahoo-commercenpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

yahoo-commerce is a confirmed malicious npm package (MAL-2026-1879) 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 yahoo-commerce (npm)

MAL-2026-1879

Immediate action

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

npm uninstall yahoo-commerce

What this malware does

The package yahoo-commerce was found to contain malicious code.

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

1d9b1475309cbeddd6421c8d19e447f33607997ef2faf0c8d6f6fc6dd9ff4a75

e3725b1c28bf27cb9ae988e61fc0c7b790b588587cef59086e7d63460f2241a9

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for yahoo-commerce (version 99.99.99).
If you installed it — respond
Remove yahoo-commerce 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 yahoo-commerce 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. yahoo-commerce 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-01662

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks yahoo-commerce-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