Malicious Code Injection in yearling_clam_z3n Package: A Threat to npm Ecosystem
Summary
MAL-2025-111262: Malicious code in yearling_clam_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 yearling_clam_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and deployment of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's infrastructure, leading to significant security concerns.
Vulnerability Detail
The vulnerability in the yearling_clam_z3n package originates from its involvement in the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain malicious scripts. Specifically, the package includes autopublish scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry, potentially leading to the distribution of compromised software.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall yearling_clam_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 yearling_clam_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like npm audit to identify and address vulnerabilities.
Conclusion
The yearling_clam_z3n package poses a significant threat to the npm ecosystem due to its malicious code that modifies package metadata and floods the registry. It is essential to take immediate action by uninstalling the package and monitoring your applications for vulnerabilities. Utilizing tools like Vulert can further enhance your security posture.
See every vulnerability recorded for yearling_clam_z3n →
FAQ
yearling_clam_z3n is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
The vulnerability can lead to the distribution of compromised software, potentially exposing your application to security risks and affecting its integrity.
You should uninstall the yearling_clam_z3n package immediately and monitor your application for any unusual behavior.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
