Malicious Code Injection in nina-enting72-breki: A Threat to npm Ecosystem
Summary
MAL-2025-74591: Malicious code in nina-enting72-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-enting72-breki' is part of a series of npm packages associated with 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. This behavior poses a significant risk to the integrity of the npm registry and can lead to the proliferation of malicious code.
Vulnerability Detail
The vulnerability stems from malicious code embedded within the 'nina-enting72-breki' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then continuously republished. This not only pollutes the npm registry but also compromises the security of applications relying on these packages. The origin of this malicious behavior is linked to the tea.xyz token reward campaign, which incentivizes such practices.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nina-enting72-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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. If you are using Vulert, you can check for vulnerabilities in your application without any installation. Simply visit the Vulert playground at https://vulert.com/scanner and upload your package-lock.json file to see if your application is affected.
Conclusion
The 'nina-enting72-breki' package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities effectively. Staying informed and proactive is key to maintaining the security of your applications.
See every vulnerability recorded for nina-enting72-breki →
FAQ
The main risk is the potential for malicious code to be executed in your application, which can compromise security and lead to data breaches.
You can use tools like Vulert to analyze your package-lock.json file for vulnerabilities without needing to install any software.
You should uninstall the package immediately and check for any dependencies that may be affected.
Currently, there are no patches available for 'nina-enting72-breki'. The best course of action is to remove the package.
Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities, ensuring your application remains secure.
