Malicious Code Injection in final_mollusk_z3n Package
Summary
MAL-2025-94507: Malicious code in final_mollusk_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 final_mollusk_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages designed to manipulate npm's registry. These packages often contain scripts that automatically generate and publish derivative packages, leading to potential security risks for developers and users alike.
Vulnerability Detail
The vulnerability in the final_mollusk_z3n package stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores through the creation of numerous derivative packages. The malicious payload can lead to the pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially introducing security risks into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall final_mollusk_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 remove the final_mollusk_z3n package from your dependencies by executing the following command: npm uninstall final_mollusk_z3n. This will prevent the execution of any malicious scripts associated with the package.
Conclusion
The final_mollusk_z3n package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is essential for developers to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.
See every vulnerability recorded for final_mollusk_z3n →
FAQ
The final_mollusk_z3n package is an npm package that has been identified as malicious, associated with the tea.xyz token reward campaign.
The vulnerability can lead to the pollution of the npm registry and may introduce security risks into your application by allowing malicious code to execute.
If you have installed the final_mollusk_z3n package, it is crucial to uninstall it immediately and check for any other affected packages.
Yes, you can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
