Malicious Code Injection in irma-tek50-breki: A Threat to npm Ecosystem
Summary
MAL-2025-73553: Malicious code in irma-tek50-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-tek50-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. These packages often contain scripts that manipulate package metadata and publish variants to inflate developer reputation scores, posing a significant risk to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'irma-tek50-breki' originates from its association with a malicious campaign that employs scripts to modify the package.json file. This includes removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants can lead to pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially compromising the security of applications that depend on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall irma-tek50-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, avoid using the 'irma-tek50-breki' package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your package dependencies to ensure they are secure.
Conclusion
The 'irma-tek50-breki' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry with variants. It is essential to remove this package from your projects and monitor your dependencies for similar vulnerabilities to maintain the security of your applications.
See every vulnerability recorded for irma-tek50-breki →
FAQ
The main risk is that it contains malicious code that can manipulate your project's package.json file and republish variants, leading to potential security vulnerabilities.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.
You should uninstall the package immediately using the command 'npm uninstall irma-tek50-breki' and review your project for any other potentially malicious packages.
Yes, consider looking for other npm packages that provide similar functionality but do not have a history of malicious activity.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to the packages you use.
