Malicious Code Injection in irma-mieayam74-breki: A Threat to npm Packages
Summary
MAL-2025-73533: Malicious code in irma-mieayam74-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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'irma-mieayam74-breki' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is linked to a token reward campaign that has been flooding the npm registry with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'irma-mieayam74-breki' stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. This behavior is intended to inflate developer reputation scores fraudulently and can lead to the proliferation of untrustworthy packages in the npm registry, posing a risk to developers and users relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall irma-mieayam74-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 measure, you can avoid using the 'irma-mieayam74-breki' package and monitor your dependencies for any signs of malicious behavior. Additionally, consider using tools like Vulert to monitor your package-lock.json file 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 'irma-mieayam74-breki' package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Taking proactive measures can help safeguard applications from such threats.
See every vulnerability recorded for irma-mieayam74-breki →
FAQ
The main issue is that it contains malicious code that modifies package.json files and floods the npm registry with untrustworthy packages.
You can check your package.json and package-lock.json files for the presence of 'irma-mieayam74-breki'. Additionally, tools like Vulert can help monitor for vulnerabilities.
Using this package can lead to the proliferation of malicious code in your project, potentially compromising your application's security and integrity.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on known vulnerabilities in the npm ecosystem.
Remove the package immediately and monitor your application for any unusual behavior. Consider using Vulert to check for other vulnerabilities.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
