Malicious Code Injection in irma-miemee75-breki: A Threat to npm Ecosystem
Summary
MAL-2025-73537: Malicious code in irma-miemee75-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-miemee75-breki' is part of a series of malicious npm packages associated with 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. The malicious nature of this package lies in its ability to modify the package.json file, remove private flags, and continuously republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability originates from the package's design to execute autopublish scripts that alter the package.json file. This manipulation allows the package to remove private flags and change version numbers, which can lead to unauthorized exposure of sensitive information and the proliferation of malicious packages in the npm registry. The continuous republishing of these variants can compromise the integrity of the npm ecosystem, making it difficult for developers to trust the packages they use.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall irma-miemee75-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 to monitor dependencies. Ensure that your project does not include 'irma-miemee75-breki' in its dependencies. You can also use the following command to audit your project for vulnerabilities: npm audit.
Conclusion
The 'irma-miemee75-breki' package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and repopulates the registry with harmful variants. It is crucial for developers to remove this package and utilize tools like Vulert to safeguard their projects against such vulnerabilities.
See every vulnerability recorded for irma-miemee75-breki →
FAQ
The primary risk is the potential exposure of sensitive information and the introduction of malicious code into your project, which can compromise the security of your application.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.
If you have installed the package, immediately remove it from your project and check for any unauthorized changes in your package.json file.
Yes, tools like Vulert can help you monitor and alert for open-source vulnerabilities in your software by analyzing your package-lock.json.
Regularly audit your dependencies, use trusted sources for packages, and employ tools like Vulert to monitor for vulnerabilities in real-time.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
