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

lintang-tea28 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158186: Malicious code in lintang-tea28 (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-tea28 is an npm package that is part of the tea.xyz token reward campaign, which has been associated with a series of malicious activities aimed at inflating developer reputation scores. This package is designed to automatically generate and publish derivative packages with randomized names, thereby polluting the npm registry and compromising the integrity of the ecosystem.

Vulnerability Detail

The vulnerability in lintang-tea28 originates from its inclusion in a malicious campaign that utilizes autopublish scripts to manipulate package.json files. The payload modifies key attributes such as removing private flags and changing version numbers, allowing the package to continuously republish variants. This not only affects the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall lintang-tea28

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, avoid using the lintang-tea28 package and monitor your project for any dependencies that may have been affected by this malicious code. Regularly check your package-lock.json file for any unauthorized changes.

Conclusion

The lintang-tea28 package poses a significant threat to the npm ecosystem due to its malicious code that manipulates package attributes and republish variants. It is essential for developers to remove this package and monitor their projects for any vulnerabilities to maintain security and trust in their applications.

See every vulnerability recorded for lintang-tea28 →

Share this vulnerability

FAQ

lintang-tea28 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising security and integrity.

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

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

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.

How To Fix

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

npm uninstall lintang-tea28

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