Malicious Code Injection in distinct_sloth_z3n Package
Summary
MAL-2025-94066: Malicious code in distinct_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 distinct_sloth_z3n package is part of the npm ecosystem, primarily used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the tea.xyz token reward system. This package is designed to automatically generate and publish derivative packages with randomized names, leading to potential pollution of the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the distinct_sloth_z3n package. It modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to the proliferation of unwanted packages in the npm registry. This not only affects the integrity of the npm ecosystem but also poses risks to developers who may inadvertently use these compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall distinct_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
As a temporary workaround, you can avoid using the distinct_sloth_z3n package and look for alternative packages that provide similar functionalities 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 distinct_sloth_z3n package poses a significant risk due to its malicious code designed to manipulate package metadata and proliferate unwanted packages. It is essential to remove this package from your projects and monitor for any similar vulnerabilities to maintain the integrity of your applications.
See every vulnerability recorded for distinct_sloth_z3n →
FAQ
distinct_sloth_z3n is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated package publishing.
The malicious code modifies your package.json file, potentially leading to the installation of unwanted packages and compromising the security of your application.
You should uninstall the distinct_sloth_z3n package immediately and check for any dependencies that may be affected.
Yes, you can use Vulert to monitor your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
