Malicious Code Injection in potential_minnow_z3n Package
Summary
MAL-2025-107168: Malicious code in potential_minnow_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 potential_minnow_z3n package is part of the npm ecosystem, often associated with token reward campaigns. These packages are designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores. This behavior makes them susceptible to malicious exploitation, particularly in the context of npm's package management system.
Vulnerability Detail
The vulnerability in the potential_minnow_z3n package originates from its association with the tea.xyz token reward campaign. It includes malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This results in the continuous republishing of these variants, which pollutes the npm registry and can lead to security risks for developers who inadvertently use these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall potential_minnow_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 avoid using the potential_minnow_z3n package altogether and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The potential_minnow_z3n package contains a serious vulnerability that can lead to malicious code injection and npm registry pollution. It is essential to uninstall this package and monitor your project for any dependencies that may be affected. Utilizing tools like Vulert can help in identifying and managing such vulnerabilities effectively.
See every vulnerability recorded for potential_minnow_z3n →
FAQ
It is an npm package associated with token reward campaigns that automates the generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry and may introduce security risks if your project inadvertently uses these malicious packages.
You should uninstall the package immediately and check for any dependencies that may rely on it.
Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
