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

lintang-tea68 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158230: Malicious code in lintang-tea68 (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-tea68 is a package within the npm ecosystem, primarily associated with the tea.xyz token reward campaign. This package, like others in its category, is designed to automate the generation and publication of derivative packages. It aims to inflate developer reputation scores for rewards related to the tea protocol. However, its functionality has been compromised, leading to significant security concerns.

Vulnerability Detail

The vulnerability in lintang-tea68 originates from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to flood the npm registry with numerous variants, thereby polluting the ecosystem and potentially harming developers' reputations. The malicious payload can lead to unauthorized access and manipulation of projects that depend on this package.

How To Fix

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

npm uninstall lintang-tea68

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 lintang-tea68 and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using a tool like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The lintang-tea68 package poses a significant security risk due to its malicious code that alters project files and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain security and integrity.

See every vulnerability recorded for lintang-tea68 →

Share this vulnerability

FAQ

lintang-tea68 is an npm package associated with the tea.xyz token reward campaign, designed to automate the publication of derivative packages.

The vulnerability can lead to unauthorized modifications in your project's package.json file, potentially compromising your project's integrity and security.

You should uninstall lintang-tea68 immediately using 'npm uninstall lintang-tea68' and check for any other affected packages.

Yes, you can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time, alerting you to any issues.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by vulnerabilities without any signup.

How To Fix

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

npm uninstall lintang-tea68

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