Malicious Code Injection in maya-ragi18-breki: A Threat to npm Packages
Summary
MAL-2025-74416: Malicious code in maya-ragi18-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-ragi18-breki' is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by generating and publishing derivative packages with altered metadata.
Vulnerability Detail
The vulnerability in 'maya-ragi18-breki' originates from its association with the tea.xyz token reward campaign, which has led to the proliferation of malicious npm packages. These packages contain scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry, potentially leading to security risks for developers who unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall maya-ragi18-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 'maya-ragi18-breki' package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The 'maya-ragi18-breki' package poses a significant risk due to its malicious code injection capabilities. It is essential for developers to remain vigilant, regularly update their dependencies, and utilize tools like Vulert to ensure their applications are secure from such vulnerabilities.
See every vulnerability recorded for maya-ragi18-breki →
FAQ
The vulnerability can lead to the injection of malicious code into your project, potentially compromising the security of your application.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time. Visit Vulert Scanner to check your application without signup.
There is no specific patch for 'maya-ragi18-breki'. The recommended action is to uninstall the package and replace it with a secure alternative.
Immediately uninstall the package using 'npm uninstall maya-ragi18-breki' and review your project for any potential security issues.
Regularly audit your dependencies, use trusted sources for packages, and employ tools like Vulert to monitor for vulnerabilities.
