Malicious Code Injection in zain-getuk51-breki: A Threat to npm Users
Summary
MAL-2025-76502: Malicious code in zain-getuk51-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 zain-getuk51-breki is part of a series of malicious npm packages linked to the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. The package's functionality is compromised, making it a vector for malicious activities.
Vulnerability Detail
The vulnerability originates from the package's malicious code, 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 these variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload can affect developers' environments and reputation, as well as the overall security of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall zain-getuk51-breki
If 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 zain-getuk51-breki package and monitor your project for any unauthorized changes. Implementing strict package management practices and using tools like Vulert can help you stay informed about vulnerabilities in your dependencies.
Conclusion
The zain-getuk51-breki package poses a significant threat to npm users due to its malicious code that manipulates the npm registry. It is crucial to remove this package from your projects and adopt best practices for dependency management to safeguard your applications.
See every vulnerability recorded for zain-getuk51-breki →
FAQ
zain-getuk51-breki is an npm package that has been identified as malicious, designed to manipulate the npm registry and inflate developer reputation scores.
The vulnerability can lead to unauthorized changes in your project, potential security risks, and pollution of the npm registry, affecting the integrity of other packages.
If you have installed zain-getuk51-breki, you should uninstall it immediately using 'npm uninstall zain-getuk51-breki' and check your project for any unauthorized changes.
Regularly update your dependencies, use trusted packages, and monitor your project with tools like Vulert to stay informed about vulnerabilities.
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 vulnerabilities using the Vulert playground without any signup.