Malicious Code Exploit in maya-soto60-breki Package
Summary
MAL-2025-74435: Malicious code in maya-soto60-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 maya-soto60-breki package 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 often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the maya-soto60-breki package stems from its malicious code that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior is intended to create derivative packages that pollute the npm registry and compromise the security of applications relying on these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall maya-soto60-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-soto60-breki package and replace it with a trusted alternative. Always verify the integrity of packages before including them in your project.
Conclusion
The maya-soto60-breki package poses a significant security risk due to its malicious code that alters package metadata and pollutes the npm registry. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in their dependencies.
See every vulnerability recorded for maya-soto60-breki →
FAQ
The vulnerability can lead to the pollution of the npm registry, compromising the security of applications that depend on this package and potentially exposing them to further attacks.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json file, you can determine if your application is affected by this vulnerability.
There is no patch for the maya-soto60-breki package itself, as it is recommended to uninstall the package entirely to mitigate the risk.
You should immediately uninstall the maya-soto60-breki package and review your project's dependencies for any other potentially malicious packages.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and only install packages from trusted sources.
