Malicious Code Injection in maya-sroto1-sluey Package
Summary
MAL-2025-88396: Malicious code in maya-sroto1-sluey (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-sroto1-sluey package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant security risks.
Vulnerability Detail
The vulnerability stems from the package's involvement in a token reward campaign that utilizes malicious scripts to manipulate package metadata. Specifically, it modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only pollutes the npm registry but also poses risks of dependency confusion and potential exploitation of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall maya-sroto1-slueyIf 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-sroto1-sluey package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The maya-sroto1-sluey package poses significant security risks due to its involvement in malicious activities aimed at manipulating the npm registry. It is crucial for developers to be aware of this vulnerability, take immediate action to remove the package, and utilize monitoring tools like Vulert to safeguard their applications.
See every vulnerability recorded for maya-sroto1-sluey →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The vulnerability can lead to dependency confusion, allowing attackers to exploit your application by injecting malicious code through compromised packages.
You should uninstall the maya-sroto1-sluey package immediately and check for any dependencies that may rely on it.
Yes, tools like Vulert can help monitor your project for open-source vulnerabilities in real-time using just the package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
