Malicious Code Injection in tomi-empal45-breki Package
Summary
MAL-2025-75688: Malicious code in tomi-empal45-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 tomi-empal45-breki package is part of the npm ecosystem and has been identified as a component of the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores in exchange for token rewards. However, it has been compromised to include malicious scripts that alter its functionality.
Vulnerability Detail
The vulnerability in the tomi-empal45-breki package originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry, potentially affecting other developers and applications that rely on npm packages. The presence of these scripts can also compromise the integrity of the development environment and lead to unintended consequences for users.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tomi-empal45-breki
If 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, avoid using the tomi-empal45-breki package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for open-source vulnerabilities in real-time.
Conclusion
The tomi-empal45-breki package has been identified as containing malicious code that can compromise the integrity of npm packages. It is crucial for developers to uninstall this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for tomi-empal45-breki →
FAQ
The tomi-empal45-breki package is part of the npm ecosystem and is associated with a token reward campaign that generates derivative packages.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your development environment, affecting other packages and applications.
You should uninstall the tomi-empal45-breki package immediately and monitor your project for any dependencies that may also be affected.
Yes, you can use Vulert to monitor your package-lock.json file for open-source vulnerabilities without requiring access to the code or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.