Malicious Code Injection in lintang-tea33: A Threat to npm Ecosystem
Summary
MAL-2025-158192: Malicious code in lintang-tea33 (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-tea33 is an npm package that is part of the tea.xyz token reward campaign, which has been associated with a series of malicious activities. This package is designed to interact with the npm registry, and its primary function is to facilitate token rewards for developers. However, it has been compromised to include scripts that manipulate package metadata and publish unauthorized variants, posing a significant risk to developers and the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in lintang-tea33 originates from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which can lead to reputation inflation for the tea protocol token rewards. This behavior not only clutters the npm registry but also compromises the security of other packages by potentially introducing malicious dependencies.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lintang-tea33If 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 lintang-tea33 and any other packages associated with the tea.xyz token reward campaign. Monitor your package-lock.json file for any unauthorized changes and consider using tools like Vulert to track vulnerabilities in your dependencies.
Conclusion
The lintang-tea33 package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for lintang-tea33 →
FAQ
lintang-tea33 is an npm package associated with the tea.xyz token reward campaign, which has been compromised to include malicious scripts.
The vulnerability can lead to unauthorized modifications in your package.json, potentially introducing malicious dependencies and cluttering the npm registry.
You should uninstall lintang-tea33 immediately using 'npm uninstall lintang-tea33' and check your project for any other compromised packages.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
