Malicious Code Injection in lilly-teadev Package: A Threat to npm Ecosystem
Summary
MAL-2025-105145: Malicious code in lilly-teadev (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 lilly-teadev package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. These packages often contain scripts that manipulate package metadata and publish variants to inflate developer reputation scores. This behavior poses a significant risk to developers and users relying on the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the lilly-teadev package originates from malicious code designed to modify the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for applications using these packages, and a compromised developer reputation system. The malicious payload can significantly disrupt the npm ecosystem by making it difficult to identify legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lilly-teadevIf 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 remove the lilly-teadev package from your project by using the following command: npm uninstall lilly-teadev. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The lilly-teadev package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry with variants. It is crucial for developers to take immediate action by updating or uninstalling the package to safeguard their applications and maintain the integrity of the npm ecosystem.
See every vulnerability recorded for lilly-teadev →
FAQ
lilly-teadev is an npm package associated with the tea.xyz token reward campaign, often containing scripts that manipulate package metadata.
The vulnerability can lead to the pollution of the npm registry, making it difficult to identify legitimate packages and potentially introducing security risks.
You should update the package to the latest patched version or uninstall it until a secure version is released.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application for vulnerabilities without requiring access to the code or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
