Malicious Code Injection in distinct_sole_z3n Package - npm Vulnerability
Summary
MAL-2025-94067: Malicious code in distinct_sole_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_sole_z3n package is part of the npm ecosystem, primarily associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, often with randomized names. It aims to inflate developer reputation scores for rewards associated with the tea protocol. However, its functionality has been compromised by malicious code that alters package metadata and floods the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the distinct_sole_z3n package. This code modifies the package.json file by removing private flags, changing version numbers, and generating random package names. It continuously republishes these variants, leading to pollution of the npm registry and potential exploitation of developers' reputations. The ramifications include unauthorized access to package management, reputation damage for developers, and potential security risks for applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall distinct_sole_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 prevent the installation of the distinct_sole_z3n package by using npm's package-lock.json file to lock your dependencies. This will help avoid the introduction of this malicious package until a secure version is available.
Conclusion
The distinct_sole_z3n package contains malicious code that poses significant risks to developers and their projects. Immediate action is required to remove this package and prevent further exploitation. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.
See every vulnerability recorded for distinct_sole_z3n →
FAQ
The distinct_sole_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of packages.
The malicious code modifies your package.json file, removes private flags, and floods the npm registry with unauthorized packages, potentially damaging your project's reputation.
You should uninstall the distinct_sole_z3n package immediately using the command npm uninstall distinct_sole_z3n and check for any dependencies that may be affected.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground without any signup.
There is no patched version of the distinct_sole_z3n package available. The best course of action is to remove the package entirely.
