Malicious Code Injection in maya-soto44-breki: A Threat to npm Ecosystem
Summary
MAL-2025-74434: Malicious code in maya-soto44-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-soto44-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 often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to developers and users alike.
Vulnerability Detail
The vulnerability in 'maya-soto44-breki' stems from its inclusion in a malicious campaign that 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 variants, polluting the npm registry and potentially compromising the integrity of dependent projects. The malicious payload is designed to exploit the npm ecosystem by creating derivative packages that can mislead users and developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall maya-soto44-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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include 'maya-soto44-breki' in its dependencies. You can also use the following command to uninstall it: npm uninstall maya-soto44-breki.
Conclusion
The 'maya-soto44-breki' package poses a significant risk due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is crucial for developers to be aware of this vulnerability and take necessary actions to protect their projects. Regular monitoring and updating of dependencies can help mitigate such risks.
See every vulnerability recorded for maya-soto44-breki →
FAQ
'maya-soto44-breki' is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project's dependencies and affecting your application's security.
If you have installed 'maya-soto44-breki', it is recommended to uninstall it immediately and check for any other affected packages in your project.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time. Vulert analyzes your package-lock.json file to provide alerts for any vulnerabilities.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
