Malicious Code Injection in lintang-tea51: A Threat to npm Ecosystem

lintang-tea51 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158212: Malicious code in lintang-tea51 (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

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 →

Share this vulnerability

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.

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback