Malicious Code Injection in kentung-77: A Threat to npm Users
Summary
MAL-2025-157561: Malicious code in kentung-77 (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-77' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. The primary function of these packages is to inflate developer reputation scores for rewards in the tea protocol, making them a potential threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'kentung-77' 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 continuous republishing of variants, polluting the npm registry and potentially compromising the security of applications that depend on these packages. The malicious scripts included in the package (such as auto.js, autopublish.js) automate this process, making it difficult for developers to track and mitigate the impact.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall kentung-77If 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 'kentung-77' and any other packages associated with the tea.xyz campaign. Regularly audit your npm packages using tools like npm audit to identify and remove any potentially malicious packages.
Conclusion
The 'kentung-77' package poses a significant threat to npm users due to its malicious behavior of modifying package files and republishing variants. It is essential to remove this package and monitor your dependencies regularly to maintain the security of your applications.
See every vulnerability recorded for kentung-77 →
FAQ
'kentung-77' is an npm package involved in a malicious campaign that aims to inflate developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially introducing malicious code into your application and compromising its security.
You should uninstall 'kentung-77' immediately using 'npm uninstall kentung-77' and audit your project for any other malicious packages.
You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
