Malicious Code Vulnerability in zero-develop-component-library - npm Package Compromise

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1880: Malicious code in zero-develop-component-library (npm). Affects zero-develop-component-library versions 99.99.2. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The zero-develop-component-library is an npm package designed to facilitate the development of reusable UI components. It is widely used in various web applications due to its ease of integration and extensive functionality. However, this package has been identified as containing malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within version 99.99.2 of the zero-develop-component-library. This code can potentially compromise the security of applications using the library, leading to unauthorized access, data breaches, or other malicious activities. The origin of this vulnerability is linked to a malicious actor who has manipulated the package to introduce harmful functionalities.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall zero-develop-component-library

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, you can remove the zero-develop-component-library from your project until a secure version is released. You can do this by executing the following command: npm uninstall zero-develop-component-library. Consider using alternative libraries that provide similar functionality without the associated risks.

Conclusion

The zero-develop-component-library has been compromised by malicious code, posing significant risks to applications that utilize it. It is essential to update to a secure version or consider alternative solutions to mitigate these risks. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for zero-develop-component-library →

Share this vulnerability

FAQ

It is an npm package used for developing reusable UI components in web applications.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without any signup.

The risks include unauthorized access to sensitive data, potential data breaches, and exploitation of the application by malicious actors.

Yes, updating to the latest version of the zero-develop-component-library will resolve the vulnerability.

As a temporary measure, consider uninstalling the package and using alternative libraries until a secure version is available.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall zero-develop-component-library

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback