Malicious Code Injection in sari-oncom38-breki Package
Summary
MAL-2025-75403: Malicious code in sari-oncom38-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-oncom38-breki 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 and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that inflate developer reputation scores for token rewards. This vulnerability poses a significant risk to developers and users relying on the integrity of npm packages.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the sari-oncom38-breki package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The primary risk is the pollution of the npm registry, which can compromise the integrity of the ecosystem and potentially introduce security risks to applications that depend on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sari-oncom38-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, you can avoid using the sari-oncom38-breki package and any other packages that may have been published as part of the same malicious campaign. Regularly audit your package.json and package-lock.json files for any suspicious entries.
Conclusion
The sari-oncom38-breki package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your projects and utilize tools like Vulert for ongoing monitoring of vulnerabilities in your dependencies.
See every vulnerability recorded for sari-oncom38-breki →
FAQ
It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to the pollution of the npm registry, potentially introducing malicious code into your application.
You should uninstall the sari-oncom38-breki package immediately and audit your dependencies for any other malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file for real-time alerts on open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
