Malicious Code Injection in sari-rangginang16-breki Package
Summary
MAL-2025-75406: Malicious code in sari-rangginang16-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 sari-rangginang16-breki package is part of the npm ecosystem, often used for various JavaScript applications. It has been identified as part of a broader campaign that exploits npm to inflate developer reputation scores through malicious practices. This package, like others in the campaign, is designed to automatically generate and publish derivative packages with randomized names, which can lead to significant pollution of the npm registry and potential security risks for developers using these packages.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the sari-rangginang16-breki package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to the proliferation of untrustworthy packages in the npm registry. The malicious payload is part of a campaign that aims to exploit the npm ecosystem for token rewards, posing risks such as reputation damage for developers and potential security breaches in applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sari-rangginang16-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 measure, avoid using the sari-rangginang16-breki package and monitor your project for any dependencies that may inadvertently include it. Regularly audit your package-lock.json file to identify and remove any malicious packages.
Conclusion
The sari-rangginang16-breki package poses a significant security risk due to its malicious code designed to manipulate npm's package ecosystem. It is crucial for developers to be vigilant, remove any affected packages, and utilize monitoring tools like Vulert to safeguard their applications from similar vulnerabilities.
See every vulnerability recorded for sari-rangginang16-breki →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the inclusion of untrustworthy packages in your application, potentially compromising its security and integrity.
You should uninstall the sari-rangginang16-breki package immediately and check for any dependencies that may rely on it.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
