Malicious Code Injection in sari-sate53-breki Package - npm Vulnerability
Summary
MAL-2025-75412: Malicious code in sari-sate53-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-sate53-breki package 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 known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in the sari-sate53-breki package stems from malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms for malicious purposes. The ramifications include compromised package integrity and potential security risks for developers relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sari-sate53-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 avoid using the sari-sate53-breki package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package dependencies for vulnerabilities.
Conclusion
The sari-sate53-breki package poses a significant security risk due to its malicious code that alters package metadata. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in their dependencies. Staying informed and proactive can help mitigate risks associated with malicious packages in the npm ecosystem.
See every vulnerability recorded for sari-sate53-breki →
FAQ
The sari-sate53-breki package is an npm package that is part of a malicious campaign aimed at manipulating package metadata for token rewards.
The vulnerability can compromise the integrity of your project by introducing malicious code that alters package metadata and potentially leads to security risks.
You should uninstall the sari-sate53-breki package immediately and check your project for any other potentially 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 by this vulnerability without requiring any signup.
