Malicious Code Injection in lentengpride-tool: npm Package Vulnerability

lentengpride-tool Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105082: Malicious code in lentengpride-tool (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

The lentengpride-tool is an npm package that has been identified as part of a broader malicious campaign targeting the npm registry. This package is designed to facilitate token reward schemes, which have been associated with the tea.xyz protocol. Its primary functionality revolves around automating the generation and publication of derivative packages, often with randomized names, to artificially inflate developer reputation scores. However, this functionality has been exploited to introduce malicious code that compromises the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in lentengpride-tool stems from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only affects the reputation of legitimate developers but also poses a risk of dependency confusion and potential exploitation of downstream projects that may unknowingly rely on these compromised packages.

How To Fix

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

npm uninstall lentengpride-tool

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 the lentengpride-tool package altogether and look for alternative packages that provide similar functionality without the associated risks. If you have already integrated this package, consider isolating it from your main application to minimize potential impacts.

Conclusion

The lentengpride-tool npm package has been identified as a vector for malicious code injection, impacting the integrity of the npm ecosystem. It is crucial for developers to be vigilant about the packages they use and to take proactive measures to secure their projects against such vulnerabilities. Regular monitoring and updates are essential to maintaining a secure development environment.

See every vulnerability recorded for lentengpride-tool →

Share this vulnerability

FAQ

Lentengpride-tool is an npm package involved in a malicious campaign aimed at inflating developer reputation scores through automated package publishing.

The vulnerability can lead to dependency confusion, potential exploitation, and pollution of the npm registry, affecting the integrity of your project's dependencies.

You should uninstall the package immediately using the command npm uninstall lentengpride-tool and review your project's dependencies for any other vulnerabilities.

Yes, tools like Vulert can help monitor and alert you in real-time for open-source vulnerabilities in your software without requiring code access.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability, without needing to sign up.

How To Fix

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

npm uninstall lentengpride-tool

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