Malicious Code Injection in tomi-bubursumsum1-breki: A Threat to npm Ecosystem
Summary
MAL-2025-75686: Malicious code in tomi-bubursumsum1-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 'tomi-bubursumsum1-breki' is part of a series of npm packages that emerged during 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 critical files and continuously pollute the npm registry.
Vulnerability Detail
The vulnerability originates from the package's malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior can lead to the proliferation of untrustworthy packages in the npm registry, potentially compromising the integrity of applications that depend on these packages. The malicious payload is designed to execute autopublish scripts that automate the creation and publication of these variants, making it difficult for developers to maintain a clean and secure package ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tomi-bubursumsum1-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 avoid using the affected package and replace it with a similar, trusted package that provides the same functionality. Always verify the source and reputation of packages before including them in your project.
Conclusion
The tomi-bubursumsum1-breki package poses a significant threat to the npm ecosystem due to its malicious code that modifies package files and publishes untrustworthy variants. It is essential for developers to remove this package from their projects and adopt best practices for dependency management to maintain security.
See every vulnerability recorded for tomi-bubursumsum1-breki →
FAQ
The package contains malicious code that modifies package.json files and publishes untrustworthy variants, compromising the npm ecosystem.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
You should uninstall the package immediately using 'npm uninstall tomi-bubursumsum1-breki' and replace it with a trusted alternative.
Yes, using this package can lead to the proliferation of malicious variants in your project, potentially compromising security and functionality.
Regularly audit your dependencies, use trusted sources for packages, and consider using tools like Vulert to monitor for vulnerabilities.
