Malicious Code Injection in dry_leopon-teagooddev: A Threat to npm Packages
Summary
MAL-2025-101786: Malicious code in dry_leopon-teagooddev (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 package 'dry_leopon-teagooddev' is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. It is designed to create and publish derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. This behavior poses significant risks to the integrity of the npm registry and the security of applications relying on these packages.
Vulnerability Detail
The vulnerability in 'dry_leopon-teagooddev' stems from its malicious code that modifies the package.json file to remove private flags and change version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This can lead to a compromised development environment, potential security breaches, and a 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 dry_leopon-teagooddevIf 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 workaround, you can avoid using the 'dry_leopon-teagooddev' package altogether. If it is a dependency of another package, consider looking for alternative packages that do not have this vulnerability. Regularly audit your npm packages using tools like npm audit to identify and address vulnerabilities.
Conclusion
The 'dry_leopon-teagooddev' package poses a significant threat due to its malicious code designed to manipulate npm packages. It is crucial to remove this package from your projects and regularly audit your dependencies to maintain a secure development environment.
See every vulnerability recorded for dry_leopon-teagooddev →
FAQ
The primary risk is the potential for malicious code to compromise your application by altering package configurations and introducing insecure dependencies.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
Regularly audit your dependencies, use tools like npm audit, and monitor for updates on vulnerabilities in the packages you use.
Immediately uninstall the package using 'npm uninstall dry_leopon-teagooddev' and review your project for any other potentially vulnerable packages.
While specific alternatives depend on your project's requirements, consider researching reputable packages that offer similar functionality without the associated risks.
