Malicious Code Exploit in kentung-25: A Threat to npm Packages

kentung-25 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157505: Malicious code in kentung-25 (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 kentung-25 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in kentung-25 originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the automatic generation and publication of derivative packages, effectively polluting the npm registry. The ramifications include compromised developer reputations and potential security risks for applications relying on these packages.

How To Fix

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

npm uninstall kentung-25

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 monitor your package dependencies using tools like Vulert. By utilizing Vulert's playground at https://vulert.com/scanner, you can check if your application is affected by this vulnerability without requiring any signup.

Conclusion

The kentung-25 package poses a significant risk due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to be vigilant and remove such packages from their projects to maintain the integrity of their applications. Utilizing tools like Vulert can help in monitoring for vulnerabilities effectively.

See every vulnerability recorded for kentung-25 →

Share this vulnerability

FAQ

Kentung-25 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your application and affecting its dependencies.

You should uninstall the kentung-25 package immediately using the command 'npm uninstall kentung-25' to mitigate any risks.

There are no patches available for kentung-25 as it is recommended to remove the package entirely from your project.

You can use Vulert to monitor your package dependencies in real-time for open-source vulnerabilities. Visit Vulert Scanner to check your application without needing to sign up.

How To Fix

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

npm uninstall kentung-25

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