Malicious Code Injection in crude_elk_z3n Package - npm Vulnerability
Summary
MAL-2025-93866: Malicious code in crude_elk_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The crude_elk_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 of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to potential security risks for developers and their projects.
Vulnerability Detail
The vulnerability in the crude_elk_z3n package originates from its association with the tea.xyz token reward campaign. This campaign has led to the creation of numerous malicious packages that include scripts designed to automatically publish derivative packages with randomized names. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random names, which can lead to the pollution of the npm registry and compromise the integrity of the packages within it.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall crude_elk_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 workaround, you can temporarily avoid using the crude_elk_z3n package and replace it with alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any changes that may indicate the presence of malicious packages.
Conclusion
The crude_elk_z3n package poses a significant security risk due to its association with a malicious campaign aimed at manipulating the npm registry. Developers should take immediate action to remove this package and monitor their projects for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for crude_elk_z3n →
FAQ
The crude_elk_z3n package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic publishing of derivative packages.
This vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project's dependencies and exposing it to further security risks.
You should immediately uninstall the crude_elk_z3n package and review your project's dependencies for any related issues. Consider using alternative packages that are not associated with malicious activities.
Yes, you can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can also check your application against known vulnerabilities using the Vulert playground without any signup.
Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and review the packages you are using to ensure they are from reputable sources.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
