Malicious Code Injection in mahesa-tempe14-breki: A Threat to npm Packages
Summary
MAL-2025-74318: Malicious code in mahesa-tempe14-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 'mahesa-tempe14-breki' is part of the npm ecosystem and has been identified as a component of the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with numerous packages that contain malicious scripts. These scripts are designed to manipulate package metadata, inflate developer reputation scores, and republish variants of the package under randomized names, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in 'mahesa-tempe14-breki' originates from its inclusion in a malicious campaign that modifies 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. This behavior can lead to significant security risks, including the potential for dependency confusion attacks and the compromise of developer accounts due to inflated reputation scores.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mahesa-tempe14-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 'mahesa-tempe14-breki' package and replace it with a trusted alternative. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'mahesa-tempe14-breki' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to uninstall this package and monitor your project for vulnerabilities using tools like Vulert. By staying vigilant and proactive, you can protect your applications from such threats.
See every vulnerability recorded for mahesa-tempe14-breki →
FAQ
The main issue is that it contains malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use Vulert to monitor your project for vulnerabilities. Visit Vulert Scanner to check your application without needing to sign up.
You should uninstall the package immediately using 'npm uninstall mahesa-tempe14-breki' and check for any other affected packages.
Yes, the malicious payload can lead to dependency confusion and potentially compromise developer accounts by inflating reputation scores.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and avoid using unverified packages from the npm registry.
