Malicious Code Injection in maya-bubur14-breki: A Threat to npm Users
Summary
MAL-2025-74383: Malicious code in maya-bubur14-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 'maya-bubur14-breki' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. Its functionality is compromised due to the presence of malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability originates from malicious code embedded in the 'maya-bubur14-breki' package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to the continuous republishing of these variants. The ramifications include pollution of the npm registry and potential exploitation of developers' reputations, making it crucial for users to be aware of this threat.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall maya-bubur14-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, users can remove the 'maya-bubur14-breki' package from their project by executing 'npm uninstall maya-bubur14-breki'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The 'maya-bubur14-breki' package poses a significant threat due to its embedded malicious code that alters package metadata and floods the npm registry. Users are advised to update or uninstall the package to protect their projects from potential exploitation.
See every vulnerability recorded for maya-bubur14-breki →
FAQ
The malicious code modifies package.json to remove private flags and changes version numbers, allowing for the creation of numerous derivative packages.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.
Using the affected package can lead to reputation damage for developers, as it floods the npm registry with malicious variants, which can be exploited.
Regularly updating packages and using tools like Vulert to monitor vulnerabilities can help prevent future issues.
If immediate updates are not possible, consider uninstalling the package to mitigate risks until a secure version is available.
