Malicious Code Injection in lintang-tea62: A Threat to npm Ecosystem
Summary
MAL-2025-158224: Malicious code in lintang-tea62 (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-tea62 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. The package's functionality is compromised by the presence of malicious scripts that manipulate its metadata and behavior.
Vulnerability Detail
The vulnerability in lintang-tea62 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 behavior not only pollutes the npm registry but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of trust in the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lintang-tea62If 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-tea62 package and monitor your project's dependencies for any instances of this package. You can also use tools like Vulert to check your application for vulnerabilities without needing to access the code directly.
Conclusion
The lintang-tea62 package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and floods the registry with compromised packages. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for lintang-tea62 →
FAQ
lintang-tea62 is an npm package associated with a token reward campaign that generates and publishes derivative packages.
The vulnerability can lead to the pollution of the npm registry and may expose your project to security risks if compromised packages are used.
You should uninstall the package immediately using the command: npm uninstall lintang-tea62.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
