Malicious Code Injection in zain-tempe31-breki: A Threat to npm Packages
Summary
MAL-2025-76547: Malicious code in zain-tempe31-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-tempe31-breki 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 the npm registry with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names.
Vulnerability Detail
The vulnerability in zain-tempe31-breki stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall zain-tempe31-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 measure, avoid using the zain-tempe31-breki package and monitor your project for any dependencies that may rely on it. Regularly check your package-lock.json for any unexpected changes or additions.
Conclusion
The zain-tempe31-breki package poses a significant threat due to its malicious behavior of modifying package files and republishing variants. It is crucial for developers to be vigilant and remove such packages from their projects to maintain security. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities in real-time.
See every vulnerability recorded for zain-tempe31-breki →
FAQ
zain-tempe31-breki is an npm package that has been identified as malicious, associated with a campaign to inflate developer reputation scores.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
You should uninstall the package immediately and check your project for any dependencies that may have been affected.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
