Malicious Code Injection in lintang-tea51: A Threat to npm Ecosystem
Summary
MAL-2025-158212: Malicious code in lintang-tea51 (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-tea51 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 publish derivative packages. However, it has been identified as containing malicious code that can compromise the integrity of the npm ecosystem. The package's primary function is to facilitate token rewards, but its malicious behavior undermines developer trust and pollutes the registry.
Vulnerability Detail
The vulnerability in lintang-tea51 originates from its design to automatically generate and publish derivative packages with randomized names. This malicious behavior is executed through scripts that modify the package.json file, removing private flags, changing version numbers, and continuously republishing variants. The ramifications include the potential for developers to unknowingly install compromised packages, leading to security breaches and loss of reputation in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lintang-tea51
If 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-tea51 package and monitor your project for any dependencies that may rely on it. Regularly audit your npm packages using tools like npm audit to identify vulnerabilities.
Conclusion
The lintang-tea51 package poses a significant threat to the npm ecosystem due to its malicious code that modifies package configurations and repopulates the registry with compromised packages. It is crucial for developers to remove this package and regularly audit their dependencies to maintain security.
See every vulnerability recorded for lintang-tea51 →
FAQ
lintang-tea51 is an npm package associated with the tea.xyz token reward campaign, designed to publish derivative packages.
The malicious code modifies your package.json, removes private flags, and can lead to the installation of compromised packages, affecting your project's security.
You should uninstall lintang-tea51 immediately using the command npm uninstall lintang-tea51 and review your dependencies for any other vulnerabilities.
You can use tools like npm audit or Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.