Malicious Code Injection in sari-tempe78-breki: npm Package Vulnerability
Summary
MAL-2025-75421: Malicious code in sari-tempe78-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-tempe78-breki' is part of the npm ecosystem and appears to be associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that modifies its own package.json file and repurposes it for nefarious activities.
Vulnerability Detail
The vulnerability originates from the package's malicious code that alters the package.json file by removing private flags and changing 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 reputation damage for developers and compromise 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-tempe78-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 prevent the installation of this malicious package by using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include 'sari-tempe78-breki' in its dependencies. You can also use the following command to audit your project for vulnerabilities: npm audit.
Conclusion
The 'sari-tempe78-breki' package poses a significant risk due to its malicious code that alters package metadata and repurposes it for harmful activities. It is crucial for developers to remove this package and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for sari-tempe78-breki →
FAQ
The impact includes potential reputation damage for developers and the risk of polluting the npm registry with malicious packages.
You can use Vulert, which monitors open-source vulnerabilities in your software by analyzing your package-lock.json file. Visit Vulert Scanner to check for vulnerabilities without any signup.
You should immediately remove the package from your project and audit your dependencies for any other vulnerabilities.
Regularly audit your dependencies using tools like npm audit and consider using Vulert for real-time monitoring of vulnerabilities.
Signs include unexpected changes in your package.json file, unusual package versions, or the presence of unfamiliar package names in your project.
