Malicious Code Vulnerability in wiz-prod Package

wiz-prod Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1875: Malicious code in wiz-prod (npm). Affects wiz-prod versions 1.0.5. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The wiz-prod package is a Node.js library used in various applications for production management. It provides functionalities that streamline deployment processes and enhance productivity. However, this package has been identified as containing malicious code, which poses significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the wiz-prod package stems from the inclusion of malicious code that can compromise the security of applications using this package. This malicious code can lead to unauthorized access, data breaches, or even complete system takeover. The vulnerability was reported by ReversingLabs and affects version 1.0.5 of the package. It is crucial for developers to address this issue promptly to safeguard their applications.

How To Fix

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

npm uninstall wiz-prod

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 wiz-prod package from your project until a secure version is released. Use the following command to uninstall it: 'npm uninstall wiz-prod'. Consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The discovery of malicious code in the wiz-prod package highlights the importance of maintaining secure coding practices and regularly updating dependencies. Developers are urged to take immediate action to mitigate risks associated with this vulnerability by updating or removing the affected package.

See every vulnerability recorded for wiz-prod →

Share this vulnerability

FAQ

The vulnerability involves malicious code that can compromise application security and lead to unauthorized access.

Version 1.0.5 of the wiz-prod package is affected by this vulnerability.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

If immediate updates are not possible, consider uninstalling the package and using alternative solutions until a secure version is available.

The vulnerability was reported by ReversingLabs, a cybersecurity firm specializing in threat detection.

How To Fix

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

npm uninstall wiz-prod

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