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

lintang-tea13 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158170: Malicious code in lintang-tea13 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

lintang-tea13 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 and manage packages. However, it has been identified as containing malicious code that can compromise the integrity of the npm ecosystem by generating and publishing derivative packages with harmful scripts.

Vulnerability Detail

The vulnerability in lintang-tea13 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, leading to pollution of the npm registry with potentially harmful packages. The autopublish scripts included in the package automate the process of creating and publishing these variants, making it difficult for users to identify and mitigate the threat.

How To Fix

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

npm uninstall lintang-tea13

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 remove the lintang-tea13 package from your project by executing the following command: npm uninstall lintang-tea13. This will prevent any malicious code from executing while you assess the situation.

Conclusion

The lintang-tea13 package poses a significant risk due to its malicious code that can compromise the npm registry. Users are urged to take immediate action by updating or uninstalling the package and utilizing tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for lintang-tea13 →

Share this vulnerability

FAQ

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

The package modifies package.json files, removes private flags, changes version numbers, and publishes derivative packages to inflate developer reputation scores.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. You can check your application using the Vulert playground at Vulert Scanner without any signup.

It is advisable to uninstall the package immediately and check for any updates or patches that may address the vulnerability.

Vulert uses just package-lock.json to monitor and alert in real-time for open-source vulnerabilities, making it easy to keep your applications secure.

How To Fix

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

npm uninstall lintang-tea13

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