Critical Malicious Code Vulnerability in @zig-design-system/react Package

@zig-design-system/react Updated 22 Sep 2026

Summary

21/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16372: Malicious code in @zig-design-system/react (npm). Affected versions are not published. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The @zig-design-system/react package is a component library designed for building user interfaces in React applications. It provides a set of reusable components that enhance development efficiency and maintainability. However, this package has been identified as containing malicious code, which poses significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the @zig-design-system/react package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it can lead to full system compromise, data breaches, and potential exploitation by external entities.

How To Fix

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

npm uninstall @zig-design-system/react

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

Currently, there are no effective workarounds to mitigate the risks posed by this vulnerability other than removing the package and securing your system.

Conclusion

The discovery of malicious code in the @zig-design-system/react package highlights the critical importance of monitoring and managing open-source dependencies. Immediate action is required to remove the package and secure any compromised systems. Utilizing tools like Vulert can aid in identifying and mitigating such vulnerabilities in the future.

See every vulnerability recorded for @zig-design-system/react →

Share this vulnerability

FAQ

You should remove the package immediately and rotate any sensitive information stored on your system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.

As of now, there is no patch available. The best course of action is to remove the package.

Failure to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential exploitation by malicious actors.

Vulert monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file, allowing you to stay informed about potential risks.

How To Fix

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

npm uninstall @zig-design-system/react

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.