Malicious Code Injection in sari-sego36-breki: A Threat to npm Packages
Summary
MAL-2025-75413: Malicious code in sari-sego36-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-sego36-breki' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. The primary function of these packages is to inflate developer reputation scores for token rewards, making them a significant concern for developers relying on npm for package management.
Vulnerability Detail
The vulnerability in 'sari-sego36-breki' originates from its malicious intent to modify the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to security risks, including the potential for unauthorized access to sensitive data and the compromise of the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sari-sego36-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-sego36-breki' package and replace it with a trusted alternative. Regularly monitor your dependencies for any updates or vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities.
Conclusion
The 'sari-sego36-breki' package poses a significant threat due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can enhance security by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for sari-sego36-breki →
FAQ
The vulnerability can lead to the manipulation of your package.json file, unauthorized access to sensitive data, and the compromise of the integrity of the npm ecosystem.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
If you have installed the package, you should immediately uninstall it using 'npm uninstall sari-sego36-breki' and check your project for any unauthorized changes.
Yes, tools like Vulert can monitor your package-lock.json file and alert you in real-time for any open-source vulnerabilities.
Regularly update your dependencies, use trusted packages, and monitor your projects for vulnerabilities using tools like Vulert.
