Malicious Code Injection in liberal_crane_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-105115: Malicious code in liberal_crane_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 liberal_crane_z3n is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in liberal_crane_z3n originates from its involvement in a malicious campaign that modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior allows the package to continuously republish variants, polluting the npm registry and potentially compromising the security of applications that depend on it. The malicious payload can lead to unauthorized access and manipulation of project dependencies.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall liberal_crane_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 liberal_crane_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using npm audit to identify and address vulnerabilities in your project's dependencies.
Conclusion
The liberal_crane_z3n package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be aware of such vulnerabilities and take proactive measures to secure their projects. By uninstalling the affected package and utilizing monitoring tools like Vulert, developers can protect their applications from potential risks.
See every vulnerability recorded for liberal_crane_z3n →
FAQ
liberal_crane_z3n is an npm package that has been identified as part of a malicious campaign to manipulate package metadata and inflate developer reputation scores.
The vulnerability can lead to unauthorized changes in your project's dependencies, potentially compromising the security and stability of your application.
You should uninstall the liberal_crane_z3n package immediately and check for any other affected packages in your project.
Yes, you can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check your application against known vulnerabilities using the Vulert playground.
Regularly audit your dependencies using npm audit, keep your packages updated, and consider using tools like Vulert to monitor for vulnerabilities.
