Malicious Code Injection in nina-tomat33-breki: A Threat to npm Ecosystem
Summary
MAL-2025-74629: Malicious code in nina-tomat33-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 'nina-tomat33-breki' is part of a series of npm packages that have been linked to a token reward campaign by tea.xyz. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses significant security risks.
Vulnerability Detail
The vulnerability in 'nina-tomat33-breki' stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This behavior can compromise the integrity of the npm registry and potentially expose users to further malicious activities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nina-tomat33-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 'nina-tomat33-breki' package and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'nina-tomat33-breki' package poses a significant risk due to its malicious behavior of modifying package.json and flooding the npm registry. It is crucial for developers to remove this package and monitor their environments for vulnerabilities to maintain security.
See every vulnerability recorded for nina-tomat33-breki →
FAQ
The main issue is that it contains malicious code that modifies package.json and floods the npm registry with derivative packages.
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 nina-tomat33-breki' and monitor for any further updates or patches.
While specific exploits have not been detailed, the behavior of the package suggests potential for further malicious activities and compromise of the npm registry.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and avoid using unverified packages from the npm registry.
