Malicious Code Injection in ida-sambel74-breki: A Threat to npm Ecosystem
Summary
MAL-2025-73453: Malicious code in ida-sambel74-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 'ida-sambel74-breki' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate npm's publishing system, often containing scripts that automatically generate and publish derivative packages. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol, making it a significant concern for developers relying on npm for package management.
Vulnerability Detail
The vulnerability in 'ida-sambel74-breki' stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in a pollution of the npm registry with potentially harmful packages that can mislead developers and compromise their applications. The malicious payload is designed to continuously republish variants, exacerbating the issue and making it difficult to track and manage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ida-sambel74-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
Currently, there are no specific workarounds to mitigate the effects of this vulnerability other than removing the affected package and monitoring your dependencies for any similar malicious packages.
Conclusion
The 'ida-sambel74-breki' package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at manipulating package publishing. Developers should take immediate action to remove this package and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for ida-sambel74-breki →
FAQ
The primary risk is that it can modify your project's package.json, leading to the publication of unauthorized packages and potential security breaches.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without needing to sign up.
Immediately uninstall the package using 'npm uninstall ida-sambel74-breki' and review your project's dependencies for any other potentially malicious packages.
No patches are available for this specific package as it is recommended to remove it entirely from your project.
Regularly audit your dependencies, use trusted packages, and consider employing tools like Vulert for real-time monitoring of vulnerabilities.
