Malicious Code Injection in kentung-56: A Threat to npm Ecosystem
Summary
MAL-2025-157538: Malicious code in kentung-56 (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'kentung-56' is part of the npm ecosystem, which is widely used for JavaScript package management. It 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 developers and users alike.
Vulnerability Detail
The vulnerability in 'kentung-56' originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these malicious variants. The ramifications include pollution of the npm registry, potential security risks for users who unknowingly install these packages, and damage to the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall kentung-56If 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 'kentung-56' package and monitor your project's dependencies for any malicious packages. Regularly audit your npm packages using 'npm audit' to identify and address vulnerabilities.
Conclusion
The 'kentung-56' package poses a significant threat to the npm ecosystem due to its malicious code that modifies package metadata. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can protect their applications from potential risks.
See every vulnerability recorded for kentung-56 →
FAQ
The primary risk is that it contains malicious code that modifies package metadata, leading to the pollution of the npm registry and potential security vulnerabilities for users.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Simply upload your package-lock.json file to check for vulnerabilities.
No, there is no patched version available for the kentung-56 package. It is recommended to uninstall it completely.
You should immediately uninstall the package using 'npm uninstall kentung-56' and audit your project for any other potentially malicious packages.
Regularly audit your dependencies, use trusted packages, and keep your packages updated to their latest versions to minimize the risk of vulnerabilities.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
