Malicious Code Injection in mahesa-rangi69-breki: A Threat to npm Users
Summary
MAL-2025-74304: Malicious code in mahesa-rangi69-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-rangi69-breki' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior poses a significant risk to the integrity of the npm registry and the security of applications that depend on these packages.
Vulnerability Detail
The vulnerability originates from malicious code embedded in the 'mahesa-rangi69-breki' package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to the continuous republishing of these variants. The ramifications include potential exposure of sensitive data, pollution of the npm registry, and the risk of dependency confusion attacks, where legitimate packages may be overshadowed by these malicious variants.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mahesa-rangi69-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-rangi69-breki' package and replace it with a trusted alternative that provides similar functionality. Additionally, consider using tools like Vulert to monitor your package dependencies for vulnerabilities.
Conclusion
The 'mahesa-rangi69-breki' package poses a significant threat due to its malicious code designed to manipulate npm registry entries. It is essential for developers to be vigilant, remove such packages, and utilize monitoring tools like Vulert to safeguard their applications against vulnerabilities.
See every vulnerability recorded for mahesa-rangi69-breki →
FAQ
It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to the pollution of the npm registry and may expose your application to security risks, including dependency confusion and data breaches.
You should uninstall the 'mahesa-rangi69-breki' package immediately and monitor your application 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 any signup.
