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

lintang-tea31 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158190: Malicious code in lintang-tea31 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

lintang-tea31 is an npm package that is part of the tea.xyz token reward campaign. This package, like others in the campaign, is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages. It typically includes scripts that automate the publishing process, making it susceptible to malicious exploitation.

Vulnerability Detail

The vulnerability in lintang-tea31 arises 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 pollute the npm registry by continuously republishing variants, thereby compromising the integrity of the package ecosystem. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs these tactics to manipulate npm's reputation system.

How To Fix

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

npm uninstall lintang-tea31

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, you can prevent the installation of this package by using npm's package-lock.json file to lock your dependencies. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities without requiring code access.

Conclusion

The lintang-tea31 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package from your project and monitor for vulnerabilities to maintain the integrity of your software.

See every vulnerability recorded for lintang-tea31 →

Share this vulnerability

FAQ

lintang-tea31 is an npm package associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores.

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

You should uninstall the lintang-tea31 package immediately and check for any dependencies that may be affected.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time using your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

How To Fix

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

npm uninstall lintang-tea31

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