Malicious Code Injection in lintang-tea58: A Threat to npm Packages

lintang-tea58 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158219: Malicious code in lintang-tea58 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

lintang-tea58 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 malicious, containing scripts that manipulate package metadata and flood the registry with derivative packages, ultimately harming the reputation of legitimate developers.

Vulnerability Detail

The vulnerability originates from the malicious code embedded in the lintang-tea58 package. This code is designed to automatically modify the package.json file by removing private flags, altering version numbers, and generating random package names. The result is a proliferation of derivative packages that can clutter the npm registry and mislead developers. The malicious payload can significantly impact the integrity of the npm ecosystem, leading to potential security risks and loss of trust in the affected packages.

How To Fix

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

npm uninstall lintang-tea58

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, you can avoid using the lintang-tea58 package and any packages that may depend on it. If you need to maintain functionality, consider using alternative packages that do not have known vulnerabilities.

Conclusion

The lintang-tea58 package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and floods the registry. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for lintang-tea58 →

Share this vulnerability

FAQ

lintang-tea58 is an npm package associated with the tea.xyz token reward campaign, which has been identified as malicious.

The malicious code modifies your package.json file and floods the npm registry with derivative packages, potentially harming your project's integrity and reputation.

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

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

npm uninstall lintang-tea58

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