Malicious Code Injection in nabila-poke74: A Threat to npm Ecosystem
Summary
MAL-2025-161276: Malicious code in nabila-poke74 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
nabila-poke74 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to manipulate developer reputation scores through the automatic generation and publishing of derivative packages. It is essential for developers to understand the risks associated with this package, as it can lead to significant security vulnerabilities within applications that rely on it.
Vulnerability Detail
The vulnerability in nabila-poke74 stems from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. This can result in compromised applications, as developers may unknowingly incorporate these malicious packages into their projects, leading to potential data breaches or system compromises.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nabila-poke74If 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 workaround, consider using a package-lock.json file to lock down your dependencies and prevent the installation of malicious packages. You can also utilize tools like Vulert to monitor your project for vulnerabilities. To check if your application is affected by this vulnerability, you can use the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The nabila-poke74 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package reputation and pollute the registry. Developers must take immediate action to remove this package and monitor their dependencies to ensure the security of their applications.
See every vulnerability recorded for nabila-poke74 →
FAQ
nabila-poke74 is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic publication of derivative packages.
The malicious code can modify your package.json file, remove private flags, and introduce random package names, potentially leading to the inclusion of harmful code in your application.
You should uninstall the package immediately using the command npm uninstall nabila-poke74 and check your project for any other affected packages.
Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and ensure you only install packages from trusted sources.
Yes, you can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
