Malicious Code Injection in applicable_mollusk_z3n: npm Package Vulnerability
Summary
MAL-2025-93254: Malicious code in applicable_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 applicable_mollusk_z3n package is part of the npm ecosystem, often used in JavaScript applications. It is designed to facilitate various functionalities within the npm environment. However, this package has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, leading to severe security risks for developers and their projects.
Vulnerability Detail
The vulnerability stems from the package being linked to a malicious campaign associated with the tea.xyz token reward initiative. It contains scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only inflates developer reputation scores but also leads to the pollution of the npm registry with potentially harmful packages. The malicious payload can compromise the integrity of applications relying on this package, leading to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall applicable_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 applicable_mollusk_z3n package from your project by executing: npm uninstall applicable_mollusk_z3n. This will prevent any malicious code from executing until a fix is applied.
Conclusion
The applicable_mollusk_z3n package poses a significant security risk due to its association with malicious code that alters project files and publishes harmful variants. It is crucial for developers to take immediate action by updating or removing the package and utilizing monitoring tools like Vulert to safeguard their applications.
See every vulnerability recorded for applicable_mollusk_z3n →
FAQ
The vulnerability involves malicious code that alters package.json files and publishes harmful variants to the npm registry.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
The risks include the compromise of application integrity, exposure to malicious packages, and potential exploitation of developer reputation systems.
Regularly update your dependencies, use tools like Vulert for monitoring, and audit your packages for known vulnerabilities.
If an immediate update is not possible, consider removing the package as a temporary measure to mitigate risks.
