Which versions of product-status are malicious?

The following npm versions of product-status are flagged malicious: 5.99.99. Treat any of these as compromised.

How do I remediate product-status if I installed it?

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

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

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

Search your lockfiles and build artifacts for product-status (version 5.99.99).

Malicious package

product-statusnpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

product-status is a confirmed malicious npm package (MAL-2026-2385) that executes malicious code on install (malicious version 5.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in product-status (npm)

MAL-2026-2385

Immediate action

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

npm uninstall product-status

What this malware does

The package product-status was found to contain malicious code.

Malicious versions

1 flagged

5.99.99

Indicators of compromise (SHA-256)

33db7cbc843b9c584c5990d006405041988fb3de3d9738c575209ded73669f8a

6b87ef85e41f2a3ee4d9e8e898f2131e8ea1b5d03c9e44368af02a6c45af73a7

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01810

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks product-status-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