Malicious Code Injection in zul-enting17-breki: A Threat to npm Ecosystem
Summary
MAL-2025-76614: Malicious code in zul-enting17-breki (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 'zul-enting17-breki' is part of a malicious campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package is designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names, which can inflate developer reputation scores for token rewards. It poses a significant risk to developers and users by polluting the npm registry with potentially harmful packages.
Vulnerability Detail
The vulnerability in 'zul-enting17-breki' originates from its malicious design to modify the package.json file, removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior can lead to a compromised npm registry, making it difficult for developers to trust the integrity of packages and potentially exposing users to security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall zul-enting17-brekiIf 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 'zul-enting17-breki' package and monitor your project for any dependencies that may inadvertently include it. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The 'zul-enting17-breki' package represents a significant threat within the npm ecosystem due to its malicious intent to manipulate the registry. Developers should take immediate action to remove this package and utilize tools like Vulert to ensure their projects remain secure from similar vulnerabilities.
See every vulnerability recorded for zul-enting17-breki →
FAQ
It is a malicious npm package involved in a campaign to inflate developer reputation scores through the creation of numerous derivative packages.
The vulnerability can lead to the pollution of the npm registry, making it difficult to trust package integrity and potentially exposing your project to security risks.
You should remove the 'zul-enting17-breki' package from your project and monitor for any updates or patches that may be released.
Yes, Vulert can monitor your package-lock.json for vulnerabilities in real-time, helping you identify if your application is affected.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
