Malicious Code Injection in sari-oncom24-breki: A Threat to npm Ecosystem
Summary
MAL-2025-75402: Malicious code in sari-oncom24-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 'sari-oncom24-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 linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality is compromised due to its involvement in autopublishing scripts that generate and publish derivative packages with randomized names, leading to pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'sari-oncom24-breki' originates from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. This behavior not only compromises the integrity of the package but also leads to the proliferation of potentially harmful packages in the npm registry, which can affect developers and users relying on legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sari-oncom24-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 remove the 'sari-oncom24-breki' package from your project by executing: 'npm uninstall sari-oncom24-breki'. This will prevent any malicious code from executing until a proper fix is applied.
Conclusion
The 'sari-oncom24-breki' package poses a significant risk due to its malicious code injection vulnerability. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can enhance security by providing real-time monitoring of vulnerabilities.
See every vulnerability recorded for sari-oncom24-breki →
FAQ
The vulnerability can lead to the injection of malicious code, which may compromise the security of applications relying on this package.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.
If an immediate update is not possible, consider removing the package as a temporary measure to prevent potential exploitation.
While specific exploits may not be publicly documented, the nature of the vulnerability suggests that it can be leveraged to publish harmful packages.
Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities, providing a proactive approach to security.
