Malicious Code Detected in strict_vicuna_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-109190: Malicious code in strict_vicuna_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
strict_vicuna_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The package's functionality is compromised, making it a vector for malicious activities.
Vulnerability Detail
The vulnerability stems from the inclusion of malicious code within the strict_vicuna_z3n package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially affecting other developers by inflating reputation scores through deceptive practices. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has flooded the npm ecosystem with similar malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall strict_vicuna_z3nIf 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 prevent the installation of the strict_vicuna_z3n package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will help avoid any accidental installations of this malicious package.
Conclusion
The strict_vicuna_z3n package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in real-time.
See every vulnerability recorded for strict_vicuna_z3n →
FAQ
strict_vicuna_z3n is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through deceptive practices.
You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to analyze your package-lock.json without any signup.
If you have installed strict_vicuna_z3n, you should uninstall it immediately using 'npm uninstall strict_vicuna_z3n' and check for any other potentially affected packages.
Yes, using this package can lead to the pollution of the npm registry, affecting other developers and potentially compromising the integrity of your project.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about the latest security advisories related to your packages.
