Malicious Code Injection in tasty_mink_z3n Package
Summary
MAL-2025-96936: Malicious code in tasty_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 tasty_mink_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate certain functionalities within the npm registry but has been compromised. It is known for its ability to generate and publish derivative packages, which can inflate developer reputation scores for token rewards. However, its malicious nature poses significant risks to developers and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the tasty_mink_z3n package stems from its inclusion in a campaign that floods the npm registry with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, ultimately polluting the npm registry and compromising the security of other packages and developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tasty_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 tasty_mink_z3n package by removing it from your dependencies. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The tasty_mink_z3n package has been identified as containing malicious code that poses significant risks to developers and the npm ecosystem. It is essential to remove this package from your projects and stay vigilant about monitoring for vulnerabilities in your dependencies.
See every vulnerability recorded for tasty_mink_z3n →
FAQ
The impact includes potential exposure to malicious code, which can compromise your project's integrity and security.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected.
If you have already used the tasty_mink_z3n package, it is crucial to uninstall it immediately and review your project for any potential security issues.
Yes, consider using other reputable packages that offer similar functionalities without the associated risks of malicious code.
Regularly check the npm registry and use tools like Vulert to monitor your dependencies for any vulnerabilities.
