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

lintang-tea70 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158233: Malicious code in lintang-tea70 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

lintang-tea70 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, which are often used to inflate developer reputation scores for token rewards. However, its functionality has been compromised, leading to significant security concerns.

Vulnerability Detail

The vulnerability in lintang-tea70 stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme to pollute the npm registry by continuously republishing variants of the package. The origin of this issue is linked to the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with malicious packages.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall lintang-tea70

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 measure, you can prevent the installation of the lintang-tea70 package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will help avoid the installation of this malicious package until a fix is implemented.

Conclusion

The lintang-tea70 package poses a significant security risk due to its malicious code that alters project files and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain security and integrity.

See every vulnerability recorded for lintang-tea70 →

Share this vulnerability

FAQ

lintang-tea70 is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The vulnerability can lead to the modification of your package.json file, potentially compromising your project's integrity and security.

You should immediately remove the lintang-tea70 package from your project and check for any unauthorized changes in your package.json file.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities using the Vulert playground without any signup.

Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and review your package.json for any unauthorized changes.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall lintang-tea70

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