Malicious Code Injection in lintang-tea32: A Threat to npm Ecosystem
Summary
MAL-2025-158191: Malicious code in lintang-tea32 (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-tea32 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in lintang-tea32 originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss 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-tea32If 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, avoid using the lintang-tea32 package and monitor your package.json and package-lock.json files for any unauthorized changes. Regularly audit your npm packages using tools like npm audit to identify and address vulnerabilities.
Conclusion
The lintang-tea32 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity and security of their applications.
See every vulnerability recorded for lintang-tea32 →
FAQ
lintang-tea32 is an npm package involved in a token reward campaign that generates and publishes derivative packages to inflate developer reputation scores.
The vulnerability can lead to unauthorized modifications in your package.json, potentially exposing your project to security risks and affecting its integrity.
You should uninstall the package immediately using 'npm uninstall lintang-tea32' and check for any dependencies that may have been affected.
You can use tools like npm audit to scan your project for vulnerabilities. Additionally, Vulert can monitor your package-lock.json for real-time alerts on open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
