Malicious Code Injection in kentung-33 Package: npm Vulnerability Overview
Summary
MAL-2025-157514: Malicious code in kentung-33 (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 kentung-33 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign associated with the tea.xyz token reward system. It is designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in the kentung-33 package stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, contributing to the proliferation of spam packages in the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly install these malicious packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall kentung-33If 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, you can avoid using the kentung-33 package and any other packages that may be part of the malicious campaign. Regularly audit your dependencies using tools like npm audit to identify and remove any potentially harmful packages.
Conclusion
The kentung-33 package poses a significant risk due to its malicious behavior, which can compromise the integrity of the npm ecosystem and affect developers' projects. It is crucial to remove this package and regularly audit your dependencies to ensure the security of your applications.
See every vulnerability recorded for kentung-33 →
FAQ
The kentung-33 package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The malicious code modifies your package.json file, potentially leading to the installation of spam packages and compromising the integrity of your project.
You should uninstall the kentung-33 package immediately using 'npm uninstall kentung-33' and audit your project for any other malicious dependencies.
Regularly audit your dependencies, use tools like npm audit, and stay updated on known vulnerabilities in the packages you use.
Vulert is a tool that monitors and alerts you in real-time for open-source vulnerabilities in your software using just package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
