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

lintang-tea39 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158198: Malicious code in lintang-tea39 (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-tea39 is an npm package that appears to be part of the tea.xyz token reward campaign. This package is designed to facilitate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. The package's functionality is compromised by malicious scripts that manipulate its metadata and behavior, leading to potential abuse within the npm registry.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the lintang-tea39 package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then continuously republished. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to 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-tea39

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-tea39 package and monitor your dependencies for any signs of malicious activity. You can also use tools like Vulert to check your package-lock.json for vulnerabilities without needing to install any software.

Conclusion

The lintang-tea39 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with compromised versions. It is crucial for developers to remove this package and monitor their dependencies to maintain the integrity of their projects.

See every vulnerability recorded for lintang-tea39 →

Share this vulnerability

FAQ

lintang-tea39 is an npm package involved in a token reward campaign that has been found to contain malicious code.

The malicious code modifies your package.json file, potentially leading to the publication of compromised packages and security risks.

You should uninstall the package immediately using npm uninstall lintang-tea39 and monitor your project for any unusual behavior.

Yes, you can use Vulert's playground at Vulert Scanner to check your application for vulnerabilities without signing up.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

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

npm uninstall lintang-tea39

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