Malicious Code Injection in indah-mie29-breki: A Threat to npm Users
Summary
MAL-2025-73488: Malicious code in indah-mie29-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-mie29-breki' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious code that alters package metadata.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the 'indah-mie29-breki' package. This payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names. It continuously republishes these variants, leading to pollution of the npm registry and potential exploitation by attackers. The ramifications include unauthorized access to sensitive data and disruption of package integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall indah-mie29-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 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 'indah-mie29-breki' in its dependencies.
Conclusion
The 'indah-mie29-breki' package poses a serious threat due to its malicious code that alters package metadata and repackages itself. It is crucial for developers to take immediate action by removing the package and monitoring their dependencies to prevent exploitation.
See every vulnerability recorded for indah-mie29-breki →
FAQ
The vulnerability involves malicious code that alters package metadata and republishes variants to the npm registry.
You can use Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without needing to sign up.
Uninstall the package immediately using 'npm uninstall indah-mie29-breki' and check for any other affected packages.
Yes, the malicious payload can lead to unauthorized access and disruption of package integrity, making it a significant risk.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to their latest secure versions.
