Malicious Code Injection in unpleasant_leech-strongdev Package
Summary
MAL-2025-110174: Malicious code in unpleasant_leech-strongdev (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 unpleasant_leech-strongdev package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of applications relying on it.
Vulnerability Detail
The vulnerability originates from the malicious payload embedded within the unpleasant_leech-strongdev package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. It continuously republishes these variants to pollute the npm registry, potentially leading to security risks for developers and users who may unknowingly install compromised packages. The ramifications include exposure to further malicious activities and degradation of the npm ecosystem's reliability.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall unpleasant_leech-strongdevIf 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 unpleasant_leech-strongdev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The unpleasant_leech-strongdev package poses a significant security risk due to its embedded malicious code. It is crucial for developers to remove this package from their projects and monitor their dependencies for any vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.
See every vulnerability recorded for unpleasant_leech-strongdev →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The vulnerability can lead to the installation of malicious code, compromising your application's security and integrity.
You should uninstall the package immediately and check your application for any unauthorized changes.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
