Malicious Code Injection in lintang-tea55: A Threat to npm Ecosystem
Summary
MAL-2025-158216: Malicious code in lintang-tea55 (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
lintang-tea55 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry and is typically used to manage dependencies in JavaScript applications. However, it has been identified as containing malicious code that can compromise the integrity of the npm ecosystem by generating and publishing derivative packages with harmful scripts.
Vulnerability Detail
The vulnerability in lintang-tea55 originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for tea protocol token rewards by flooding the npm registry with numerous derivative packages. The implications of this vulnerability include potential pollution of the npm registry, increased security risks for developers using affected packages, and a degradation of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lintang-tea55If 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 lintang-tea55 package from your project by executing the following command: npm uninstall lintang-tea55. This will prevent any malicious code from executing while you assess the situation and look for alternative packages.
Conclusion
The lintang-tea55 package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and floods the registry. It is crucial for developers to take immediate action by uninstalling the package and monitoring their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.
See every vulnerability recorded for lintang-tea55 →
FAQ
lintang-tea55 is an npm package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.
The malicious code can modify your package.json file, remove private flags, and flood the npm registry with derivative packages, potentially compromising your project's integrity.
You should uninstall the lintang-tea55 package immediately and check for any other affected packages in your project.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities using the Vulert playground without any signup.
Regularly update your dependencies, use tools like Vulert to monitor for vulnerabilities, and review package sources before installation.
