Malicious Code Injection in lintang-tea66: A Threat to npm Packages

lintang-tea66 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158228: Malicious code in lintang-tea66 (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-tea66 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm ecosystem, allowing developers to publish and manage packages. However, it has been identified as containing malicious code that can compromise the integrity of the npm registry and the reputation of developers using it.

Vulnerability Detail

The vulnerability in lintang-tea66 originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for token rewards by flooding the npm registry with derivative packages. The ramifications include potential pollution of the npm registry, loss of developer trust, and increased difficulty in managing legitimate packages.

How To Fix

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

npm uninstall lintang-tea66

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 workaround, you can monitor your project for any unauthorized changes by using tools like Vulert. To check if your application is affected by this vulnerability, you can use the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The lintang-tea66 package poses a significant threat due to its malicious code designed to manipulate package metadata and flood the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for lintang-tea66 →

Share this vulnerability

FAQ

lintang-tea66 is an npm package associated with the tea.xyz token reward campaign, which has been identified to contain malicious code.

The malicious code modifies your package.json file, potentially leading to unauthorized changes and pollution of the npm registry.

You should uninstall the lintang-tea66 package immediately using the command: npm uninstall lintang-tea66.

You can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by vulnerabilities without any signup.

How To Fix

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

npm uninstall lintang-tea66

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