Malicious Code Injection in nina-getuk35-breki: A Threat to npm Users
Summary
MAL-2025-74596: Malicious code in nina-getuk35-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-getuk35-breki' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, posing a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'nina-getuk35-breki' originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This not only compromises the security of the affected packages but also affects the overall trustworthiness of the npm ecosystem, potentially leading to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nina-getuk35-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-getuk35-breki' package and monitor your project for any unauthorized changes to your package.json file. Implementing strict access controls and using tools like Vulert can help you monitor for vulnerabilities in real-time.
Conclusion
The 'nina-getuk35-breki' package poses a significant threat to npm users due to its malicious behavior aimed at manipulating the npm registry. It is crucial to remove this package from your projects and monitor for vulnerabilities using tools like Vulert to maintain the integrity of your software.
See every vulnerability recorded for nina-getuk35-breki →
FAQ
It is a malicious npm package that is part of a campaign to manipulate the npm registry and inflate developer reputation scores.
The vulnerability can lead to unauthorized changes in your project's dependencies, potentially compromising security and stability.
You should uninstall the package immediately using 'npm uninstall nina-getuk35-breki' and review your project for any unauthorized changes.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
