Malicious Code Injection in sari-sambel24-ruro Package
Summary
MAL-2025-108382: Malicious code in sari-sambel24-ruro (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 sari-sambel24-ruro package 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 exploits npm's publishing mechanisms, leading to significant security concerns.
Vulnerability Detail
The vulnerability stems from the package being associated with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to modify the package.json file, removing private flags and altering version numbers. The malicious payload generates random package names, which can lead to reputation inflation for developers involved in the tea.xyz token reward scheme. This not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sari-sambel24-ruro
If 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 measure, you can avoid using the sari-sambel24-ruro 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 sari-sambel24-ruro package is a clear example of how malicious actors can exploit open-source ecosystems. By understanding the nature of this vulnerability and taking appropriate actions, developers can protect their applications from potential threats. Regular monitoring and updating of dependencies are essential practices for maintaining security.
See every vulnerability recorded for sari-sambel24-ruro →
FAQ
sari-sambel24-ruro is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
Using this package can compromise your application's security, potentially leading to unauthorized access or manipulation of your code.
You should uninstall the package immediately using the command npm uninstall sari-sambel24-ruro and review your dependencies for any other malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.