Malicious Code Injection in sore_sloth_z3n Package - npm Vulnerability
Summary
MAL-2025-96673: Malicious code in sore_sloth_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 sore_sloth_z3n package is part of the npm ecosystem and has been identified as part of a malicious campaign associated with the tea.xyz token reward initiative. This package is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names, which can inflate developer reputation scores for token rewards. The presence of such malicious code poses significant risks to developers and users relying on this package for legitimate purposes.
Vulnerability Detail
The vulnerability in the sore_sloth_z3n package originates from its malicious intent to modify the package.json file by removing private flags, altering version numbers, and creating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of the ecosystem. Developers using this package may unknowingly contribute to the proliferation of malicious packages, risking their reputation and the security of their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sore_sloth_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
Currently, there are no specific workarounds to mitigate the effects of this vulnerability other than removing the affected package. It is advisable to monitor your dependencies regularly and utilize tools like Vulert to check for vulnerabilities in your package-lock.json file.
Conclusion
The sore_sloth_z3n package presents a significant security risk due to its malicious code designed to manipulate the npm registry. Developers are advised to remove this package from their projects and monitor their dependencies for any vulnerabilities. Utilizing tools like Vulert can help in identifying potential risks in real-time.
See every vulnerability recorded for sore_sloth_z3n →
FAQ
sore_sloth_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 proliferation of malicious packages, compromising the integrity of your application and potentially affecting its reputation.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
If you have used the sore_sloth_z3n package, it is recommended to uninstall it immediately and review your dependencies for any potential risks.
There are no patches available for the sore_sloth_z3n package. The best course of action is to remove the package entirely.
