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

lintang-tea59 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158220: Malicious code in lintang-tea59 (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-tea59 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry and is typically used for publishing and managing JavaScript 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 altered metadata.

Vulnerability Detail

The vulnerability in lintang-tea59 originates from its inclusion in a campaign that floods the npm registry with malicious packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. This can result in developers inadvertently using compromised packages, which may lead to security breaches or loss of reputation.

How To Fix

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

npm uninstall lintang-tea59

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 workaround, you can monitor your package dependencies using tools like Vulert. By utilizing Vulert, you can check your package-lock.json file for vulnerabilities without needing to install any software. You can access the Vulert playground at https://vulert.com/scanner to see if your application is affected by this vulnerability.

Conclusion

The lintang-tea59 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and publish unauthorized derivatives. It is crucial for developers to remove this package and utilize tools like Vulert to monitor their dependencies for vulnerabilities.

See every vulnerability recorded for lintang-tea59 →

Share this vulnerability

FAQ

lintang-tea59 is an npm package that is part of a campaign aimed at generating token rewards through the publication of numerous derivative packages.

The malicious code can modify your package.json file, remove private flags, and publish altered versions of your packages, leading to potential security risks.

You should uninstall lintang-tea59 immediately using 'npm uninstall lintang-tea59' to prevent any potential security issues.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to minimize the risk of vulnerabilities.

You can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without any signup.

How To Fix

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

npm uninstall lintang-tea59

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