Malicious Code Injection in general_mink_z3n Package - npm Vulnerability Overview
Summary
MAL-2025-94661: Malicious code in general_mink_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 general_mink_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of these packages is to facilitate token rewards by manipulating developer reputation scores through automated publishing scripts.
Vulnerability Detail
The vulnerability in the general_mink_z3n package arises from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to pollute the npm registry by continuously republishing variants, thereby inflating the reputation scores of developers involved in the tea protocol token rewards. The origin of this vulnerability is linked to the broader issue of malicious packages flooding the npm ecosystem, which poses significant risks to developers and users relying on these packages for their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall general_mink_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 workaround, you can temporarily avoid using the general_mink_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package.json file is regularly audited for any unauthorized changes.
Conclusion
The general_mink_z3n package poses a significant risk due to its malicious code that alters project files and inflates developer reputation scores. It is crucial to uninstall this package and monitor your dependencies to safeguard your projects from such vulnerabilities.
See every vulnerability recorded for general_mink_z3n →
FAQ
The general_mink_z3n package is an npm package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.
The malicious code modifies your package.json file, removes private flags, and can lead to the continuous republishing of variants, which can compromise your project's integrity.
If you have installed the general_mink_z3n package, you should uninstall it immediately using npm uninstall general_mink_z3n.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file. You can check for vulnerabilities in your application using the Vulert playground at Vulert Scanner without any signup.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the npm ecosystem.
