Malicious Code Injection in kentung-81 Package: A Threat to npm Users

kentung-81 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157566: Malicious code in kentung-81 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The kentung-81 package is part of a broader campaign that exploits npm's ecosystem by flooding it with malicious packages. These packages are designed to manipulate developer reputation scores through automated scripts that publish derivative packages with randomized names. This behavior not only affects the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages.

Vulnerability Detail

The vulnerability in the kentung-81 package originates from its involvement in the tea.xyz token reward campaign. It contains scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This malicious behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the security of applications that depend on these packages.

How To Fix

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

npm uninstall kentung-81

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, avoid using the kentung-81 package and monitor your dependencies for any similar malicious packages. You can also utilize tools like Vulert to scan your package-lock.json file for vulnerabilities.

Conclusion

The kentung-81 package poses a significant threat to npm users due to its malicious code that manipulates package metadata and floods the npm registry. It is crucial to remove this package and regularly monitor your dependencies to maintain the security of your applications.

See every vulnerability recorded for kentung-81 →

Share this vulnerability

FAQ

The kentung-81 package is a malicious npm package that is part of a campaign to inflate developer reputation scores through automated publishing of derivative packages.

The vulnerability can lead to the introduction of compromised code into your application, potentially exposing it to security risks and instability.

You should immediately uninstall the kentung-81 package and review your project's dependencies for any other malicious packages.

Yes, regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and avoid using unverified packages.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check for vulnerabilities without any installation through the Vulert playground.

How To Fix

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

npm uninstall kentung-81

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