Malicious Code Injection in Inevitable Smelt Z3N Package
Summary
MAL-2025-95011: Malicious code in inevitable_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
Background
The 'inevitable_smelt_z3n' package is part of the npm ecosystem and appears to be associated with the tea.xyz token reward campaign. This package is designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is compromised by malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in the 'inevitable_smelt_z3n' package stems from malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The origin of this issue is linked to the package's involvement in a token reward scheme, which incentivizes the creation of numerous derivative packages, ultimately compromising the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall inevitable_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 remove the 'inevitable_smelt_z3n' package from your project by executing the command: 'npm uninstall inevitable_smelt_z3n'. This will prevent any malicious code from executing while you seek a secure alternative package.
Conclusion
The 'inevitable_smelt_z3n' package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to take immediate action by updating or removing the package to safeguard your project. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.
See every vulnerability recorded for inevitable_smelt_z3n →
FAQ
It is an npm package involved in automating the generation of derivative packages for token rewards, which has been found to contain malicious code.
The malicious code modifies your package.json file, potentially exposing your project to security risks and polluting the npm registry with unwanted packages.
You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.
Yes, you can use tools like Vulert, which monitors your package-lock.json 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.
