Malicious Code Injection in nina-brengkes81-breki Package - npm Vulnerability
Summary
MAL-2025-122077: Malicious code in nina-brengkes81-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 nina-brengkes81-breki package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package compromises its integrity and poses significant risks to developers and their projects.
Vulnerability Detail
The vulnerability stems from the package being associated with a token reward campaign that floods the npm registry with malicious packages. It includes scripts designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the pollution of the npm registry, making it difficult for developers to trust the integrity of packages. The malicious payload can potentially compromise applications that depend on this package, leading to security breaches and loss of data.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nina-brengkes81-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
There are no direct workarounds for this vulnerability other than removing the affected package. If your application relies on functionalities provided by this package, consider looking for alternative packages that offer similar features without the associated risks.
Conclusion
The nina-brengkes81-breki package poses a significant security risk due to its malicious code designed to manipulate package metadata and pollute the npm registry. Immediate action is required to remove this package from any projects to safeguard against potential vulnerabilities.
See every vulnerability recorded for nina-brengkes81-breki →
FAQ
The nina-brengkes81-breki package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
This vulnerability can compromise the integrity of your application by introducing malicious code that modifies your package.json file and pollutes the npm registry, leading to potential security breaches.
You should uninstall the nina-brengkes81-breki package immediately using the command npm uninstall nina-brengkes81-breki and check your package-lock.json for any references to it.
Currently, there is no patched version available for the nina-brengkes81-breki package, so the best action is to remove it completely.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just the package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner without any signup.
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.