Malicious Code Injection in nina-enting75-breki: A Threat to npm Users
Summary
MAL-2025-74592: Malicious code in nina-enting75-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-enting75-breki' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing numerous derivative packages with randomized names. This behavior not only clutters the npm registry but also poses a significant risk to developers who may unknowingly install these compromised packages.
Vulnerability Detail
The vulnerability in 'nina-enting75-breki' stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially leading to security issues for developers who rely on these packages. The origin of this vulnerability is linked to a broader campaign aimed at exploiting npm's package management system for token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nina-enting75-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 measure, you can avoid using the 'nina-enting75-breki' package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package.json and package-lock.json files to ensure no malicious packages are present.
Conclusion
The 'nina-enting75-breki' package represents a significant security risk due to its malicious behavior aimed at manipulating npm's package management system. Developers should take immediate action to remove this package and implement best practices for dependency management to safeguard their projects.
See every vulnerability recorded for nina-enting75-breki →
FAQ
The main threat is the modification of your package.json file, which can lead to the installation of other malicious packages and compromise your project's integrity.
You can use tools like Vulert to monitor your package-lock.json for vulnerabilities. Visit the Vulert playground at Vulert Scanner to check if your application is affected.
You should uninstall the 'nina-enting75-breki' package immediately using the command 'npm uninstall nina-enting75-breki' and audit your project for any other malicious packages.
Yes, tools like Vulert can help monitor and alert you in real-time for open-source vulnerabilities in your software without requiring code access or installation.
Regularly update your dependencies, use trusted packages, and utilize vulnerability scanning tools to keep your project secure.
