Malicious Code Injection in mahesa-sate82-breki Package - npm Vulnerability
Summary
MAL-2025-74308: Malicious code in mahesa-sate82-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 mahesa-sate82-breki package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, this package has been identified as part of a malicious campaign associated with the tea.xyz token reward system, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages.
Vulnerability Detail
The vulnerability in the mahesa-sate82-breki package stems from its malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to clutter the npm registry. This behavior can lead to security risks, including the potential for developers to unknowingly use compromised packages, which can affect the integrity of their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mahesa-sate82-breki
If 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 mahesa-sate82-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 mahesa-sate82-breki package poses a significant security risk due to its malicious code designed to manipulate package metadata and clutter the npm registry. It is crucial for developers to remove this package from their projects and utilize tools like Vulert for ongoing monitoring of vulnerabilities.
See every vulnerability recorded for mahesa-sate82-breki →
FAQ
mahesa-sate82-breki is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising its security and integrity.
You should uninstall the mahesa-sate82-breki package immediately and monitor your project for any unusual behavior.
Yes, tools like Vulert can help monitor your package dependencies for vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.