Which versions of zero-develop-component-library are malicious?

The following npm versions of zero-develop-component-library are flagged malicious: 99.99.2. Treat any of these as compromised.

How do I remediate zero-develop-component-library if I installed it?

Remove zero-develop-component-library 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 zero-develop-component-library — how do I know if it already compromised me?

If zero-develop-component-library 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 zero-develop-component-library part of a known attack campaign?

Yes — zero-develop-component-library is associated with the RLMA-2026-01671 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 zero-develop-component-library across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for zero-develop-component-library (version 99.99.2).

Malicious package

zero-develop-component-librarynpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

zero-develop-component-library is a confirmed malicious npm package (MAL-2026-1880) that executes malicious code on install (malicious version 99.99.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in zero-develop-component-library (npm)

MAL-2026-1880

Immediate action

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

npm uninstall zero-develop-component-library

What this malware does

The package zero-develop-component-library was found to contain malicious code.

Malicious versions

1 flagged

99.99.2

Indicators of compromise (SHA-256)

fb5276c34ca4f94e2bd07e6b813068a6c0b9e379439d246159f5246cb98a2c7e

b25ede928413a72b6cfc25c807bc6f5902bd1b9d00f1d3d83624e237da613fb1

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01671

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks zero-develop-component-library-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