Malicious Code Injection in mechanical_smelt_z3n Package
Summary
MAL-2025-105750: Malicious code in mechanical_smelt_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 mechanical_smelt_z3n package is part of the npm ecosystem, often used in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the generation of derivative packages. This package, like others in the campaign, is designed to automatically publish variants with altered metadata, making it a significant risk for developers relying on it.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign associated with the tea.xyz token reward initiative. It includes scripts that modify the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to pollution of the npm registry and can compromise the integrity of projects that depend on this package, potentially leading to security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mechanical_smelt_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 mechanical_smelt_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.
Conclusion
The mechanical_smelt_z3n package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to be aware of such vulnerabilities and take proactive measures to secure their projects by removing affected packages and utilizing monitoring tools like Vulert.
See every vulnerability recorded for mechanical_smelt_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to the modification of your project's package.json file and the introduction of malicious code, compromising your project's integrity.
You should immediately uninstall the mechanical_smelt_z3n package and check for any dependencies that may be affected.
Yes, tools like Vulert can help monitor your project 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.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
