Malicious Code Injection in indah-ragi26-breki: A Threat to npm Packages
Summary
MAL-2025-73496: Malicious code in indah-ragi26-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 'indah-ragi26-breki' 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. The primary functionality of such packages is to inflate developer reputation scores through automated publishing scripts, leading to potential security risks.
Vulnerability Detail
The vulnerability in 'indah-ragi26-breki' stems from its malicious code designed to manipulate the package.json file. This code removes private flags, alters version numbers, and generates random package names, thereby republishing variants to pollute the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms to create a large number of derivative packages, potentially leading to reputation damage and security breaches for developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall indah-ragi26-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 'indah-ragi26-breki' package and monitor your project for any dependencies that may inadvertently include it. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The 'indah-ragi26-breki' package poses a significant risk due to its malicious code that alters package configurations and repopulates the npm registry with harmful variants. It is crucial for developers to remain vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for indah-ragi26-breki →
FAQ
The main threat is the malicious code that modifies package.json, potentially leading to security vulnerabilities and reputation damage.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
You should uninstall the package immediately using 'npm uninstall indah-ragi26-breki' and check your project for any other affected dependencies.
Yes, tools like Vulert can monitor your package-lock.json in real-time for open-source vulnerabilities.
Ignoring this vulnerability can lead to security breaches, unauthorized access to your project, and damage to your reputation as a developer.
