Malicious Code Injection in zul-klentik75-breki: A Threat to npm Ecosystem
Summary
MAL-2025-76623: Malicious code in zul-klentik75-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
Background
The package 'zul-klentik75-breki' is part of a series of malicious npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol, making it a significant concern for developers relying on npm for package management.
Vulnerability Detail
The vulnerability in 'zul-klentik75-breki' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants that pollute the npm registry, potentially leading to security risks for developers who may unknowingly integrate these compromised packages into their projects. The malicious scripts included in the package (such as auto.js and autopublish.js) automate this harmful behavior, making it difficult for users to detect the issue.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall zul-klentik75-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-klentik75-breki' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert, which alerts you to open-source vulnerabilities in real-time based on your package-lock.json file.
Conclusion
The 'zul-klentik75-breki' package poses a significant threat to the npm ecosystem due to its malicious behavior of manipulating package metadata and republishing variants. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can enhance security by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for zul-klentik75-breki →
FAQ
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising security and functionality.
You can use Vulert to monitor your package-lock.json file for vulnerabilities without needing to install any additional software.
Immediately uninstall the package using 'npm uninstall zul-klentik75-breki' and check for any alternative packages.
Yes, tools like Vulert can help you monitor and alert for open-source vulnerabilities in your software in real-time.
Regularly audit your dependencies, use tools like Vulert, and stay updated on security advisories related to the packages you use.
