Malicious Code Injection in voinzaril: npm Package Vulnerability

voinzaril Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-91983: Malicious code in voinzaril (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 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

voinzaril is an npm package that has been implicated in a malicious campaign associated with the tea.xyz token reward system. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores. The functionality of voinzaril is compromised due to its involvement in this malicious activity, making it a target for developers who rely on npm for package management.

Vulnerability Detail

The vulnerability in voinzaril stems from its association with a malicious campaign that modifies the package.json file by removing private flags and altering version numbers. This allows the package to continuously republish variants with randomized names, polluting the npm registry. The malicious payload can lead to unauthorized access and manipulation of developer environments, potentially compromising the integrity of applications that depend on this package.

How To Fix

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

npm uninstall voinzaril

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 voinzaril package from your project by executing the following command in your terminal: npm uninstall voinzaril. This will prevent any malicious code from executing in your application.

Conclusion

The voinzaril package has been identified as a vector for malicious code injection, posing significant risks to applications that utilize it. Immediate action is required to remove this package and safeguard your development environment. Regular monitoring for vulnerabilities is essential to maintain application security.

See every vulnerability recorded for voinzaril →

Share this vulnerability

FAQ

voinzaril is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to unauthorized modifications in your application's dependencies, potentially compromising its security and integrity.

You should immediately uninstall the voinzaril package from your project to mitigate any risks associated with the vulnerability.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software without requiring access to the code or installation.

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

How To Fix

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

npm uninstall voinzaril

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