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

lintang-tea91 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158256: Malicious code in lintang-tea91 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

lintang-tea91 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry, potentially allowing developers to gain reputation scores through the publication of derivative packages. However, it has been identified as containing malicious scripts that compromise its integrity and the security of the npm ecosystem.

Vulnerability Detail

The vulnerability in lintang-tea91 originates from its inclusion in a campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry, making it difficult for users to find legitimate packages. The malicious payload can lead to unauthorized access and manipulation of package data, posing significant risks to developers and users alike.

How To Fix

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

npm uninstall lintang-tea91

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 avoid using the lintang-tea91 package and any other related packages until a secure version is released. Monitor your package-lock.json file for any signs of malicious packages and remove them promptly.

Conclusion

The lintang-tea91 package poses a significant threat to the npm ecosystem due to its malicious code that alters package data and inflates developer reputation scores. It is crucial for developers to remove this package and monitor their dependencies for similar vulnerabilities to ensure the security of their projects.

See every vulnerability recorded for lintang-tea91 →

Share this vulnerability

FAQ

lintang-tea91 is an npm package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.

The malicious code modifies your package.json file, removes private flags, and publishes derivative packages, which can compromise your project's integrity and security.

You should uninstall lintang-tea91 immediately using the command 'npm uninstall lintang-tea91' and check for any other related malicious packages.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check your application for this vulnerability using the Vulert playground without any signup.

Currently, there are no patches available for lintang-tea91. The best course of action is to remove the package from your project.

How To Fix

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

npm uninstall lintang-tea91

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