Malicious Code Injection in sparkling_vole_z3n Package
Summary
MAL-2025-108971: Malicious code in sparkling_vole_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
The sparkling_vole_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability originates from the package's malicious payload that modifies the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to reputation damage for developers and potential security risks for users who inadvertently install these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sparkling_vole_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 remove the sparkling_vole_z3n package from your project by executing the following command: npm uninstall sparkling_vole_z3n. This will prevent any potential exploitation of the vulnerability until a fixed version is available.
Conclusion
The sparkling_vole_z3n package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry with compromised packages. It is essential to take immediate action by uninstalling the package and monitoring for updates to ensure the security of your applications.
See every vulnerability recorded for sparkling_vole_z3n →
FAQ
The main issue is that it contains malicious code that modifies package.json files and republishes variants to the npm registry, which can lead to security vulnerabilities.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By using the Vulert playground at Vulert Scanner, you can check if your application is affected without needing to sign up.
If you have installed the sparkling_vole_z3n package, you should uninstall it immediately and check for any other affected packages in your project.
Currently, there is no specific patched version mentioned. It is advisable to monitor the package repository for updates and patches.
Using this package can lead to security risks such as unauthorized access to your project, reputation damage, and potential exploitation by malicious actors.
