Malicious Code Injection in honest_mink_z3n: A Threat to npm Packages
Summary
MAL-2025-94855: Malicious code in honest_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 package 'honest_mink_z3n' 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 for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from malicious code embedded within the 'honest_mink_z3n' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and a compromised reputation system within the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall honest_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 temporary workaround, avoid using the 'honest_mink_z3n' package and monitor your project for any dependencies that may indirectly include it. Regularly check your package-lock.json file for any signs of this malicious package.
Conclusion
The 'honest_mink_z3n' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies to maintain the integrity of their projects.
See every vulnerability recorded for honest_mink_z3n →
FAQ
The impact includes potential security risks, pollution of the npm registry, and compromised developer reputation scores.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Check your application using the Vulert playground at Vulert Scanner.
You should uninstall the package immediately using 'npm uninstall honest_mink_z3n' and check for any other affected dependencies.
Currently, there is no specific patch for the 'honest_mink_z3n' package. The best course of action is to remove the package entirely.
Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities without requiring code access or installation.
