Malicious Code Injection in lintang-tea99: A Threat to npm Users

lintang-tea99 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158264: Malicious code in lintang-tea99 (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-tea99 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry, allowing developers to publish their packages and contribute to the ecosystem. However, it has been identified as a malicious package that employs scripts to manipulate its own metadata and create numerous derivative packages, which can lead to reputation inflation and registry pollution.

Vulnerability Detail

The vulnerability in lintang-tea99 originates from its malicious code, which modifies the package.json file to remove private flags and alter version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly install these malicious packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall lintang-tea99

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 use the following command to prevent the installation of the lintang-tea99 package and its derivatives: npm audit fix --force. This command will help identify and fix vulnerabilities in your project, but be cautious as it may also update other packages.

Conclusion

The lintang-tea99 package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and creates derivative packages. It is crucial for developers to be vigilant, remove any affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for lintang-tea99 →

Share this vulnerability

FAQ

lintang-tea99 is an npm package associated with the tea.xyz token reward campaign, which has been identified as malicious due to its harmful scripts.

The malicious code modifies your package.json file, removes private flags, and creates numerous unwanted derivative packages, which can lead to security vulnerabilities.

You should uninstall the package immediately using the command npm uninstall lintang-tea99 and check for any other affected packages.

Yes, regularly audit your dependencies using tools like npm audit and consider using Vulert to monitor your project for vulnerabilities in real-time.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file, without requiring code access or installation.

How To Fix

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

npm uninstall lintang-tea99

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