Malicious Code Injection in kentung-76 Package: A Threat to npm Users
Summary
MAL-2025-157560: Malicious code in kentung-76 (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-76 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 npm with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores for token rewards, making them a significant threat to users and developers alike.
Vulnerability Detail
The vulnerability in the kentung-76 package originates from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also exposes users to potential security risks, as these packages can be used to distribute harmful code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall kentung-76If 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, users can avoid using the kentung-76 package and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner.
Conclusion
The kentung-76 package poses a significant threat to npm users due to its malicious code that alters package metadata. Immediate action is required to remove this package and monitor for vulnerabilities using tools like Vulert. Staying informed and proactive is essential to maintaining the security of your projects.
See every vulnerability recorded for kentung-76 →
FAQ
The kentung-76 package is an npm package associated with the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.
The vulnerability can lead to the modification of your package.json file, potentially exposing your project to security risks and affecting the integrity of the npm ecosystem.
You should immediately remove the kentung-76 package from your project and check for any updates or patches that may be available.
Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by the kentung-76 vulnerability.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
