Malicious Code Injection in Autonomous Mink Z3N: A Threat to NPM Packages
Summary
MAL-2025-99669: Malicious code in autonomous_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 'autonomous_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 scripts that compromise its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability in 'autonomous_mink_z3n' originates from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the pollution of the npm registry and can potentially harm developers by affecting their reputation and the integrity of their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall autonomous_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, you can avoid using the 'autonomous_mink_z3n' package altogether. If it is already in use, consider removing it from your package.json and running 'npm install' to clean up your dependencies.
Conclusion
The 'autonomous_mink_z3n' package poses a significant risk 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 autonomous_mink_z3n →
FAQ
The vulnerability involves malicious code that modifies package.json, removes private flags, and generates random package names, leading to npm registry pollution.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.
You should remove the 'autonomous_mink_z3n' package from your project and update your dependencies to ensure your application is secure.
While specific exploits have not been detailed, the malicious behavior of the package can lead to reputation damage and potential security risks for developers.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to minimize the risk of vulnerabilities.
