Malicious Code Injection in irma-gembus31-breki: A Threat to npm Users
Summary
MAL-2025-73516: Malicious code in irma-gembus31-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 'irma-gembus31-breki' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to manipulate npm's publishing system, generating numerous derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, but this comes at the cost of security and integrity within the npm registry.
Vulnerability Detail
The vulnerability in 'irma-gembus31-breki' originates from its inclusion in a malicious campaign that floods the npm registry with spam packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these malicious packages, potentially leading to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall irma-gembus31-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-gembus31-breki' package altogether. If you must use it, consider isolating it in a separate environment and monitor your application closely for any unusual behavior.
Conclusion
The 'irma-gembus31-breki' package poses a significant risk due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and monitor their applications for any unusual behavior. Utilizing tools like Vulert can aid in identifying vulnerabilities and ensuring the security of your software.
See every vulnerability recorded for irma-gembus31-breki →
FAQ
The malicious code can lead to the pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially exposing them to security risks.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Simply upload your package-lock.json file to the Vulert playground at Vulert Scanner to check for vulnerabilities.
To prevent similar vulnerabilities, always review package dependencies, use trusted sources, and regularly update your packages to their latest versions.
If you have installed 'irma-gembus31-breki', immediately uninstall it using 'npm uninstall irma-gembus31-breki' and check your project for any other potentially malicious packages.
Yes, you can report vulnerabilities to npm by following their security reporting guidelines, which help in maintaining the integrity of the npm ecosystem.
