Malicious Code Injection in nabila-poke72: A Threat to npm Users
Summary
MAL-2025-161274: Malicious code in nabila-poke72 (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 nabila-poke72 is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and deployment of applications. However, it 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. This vulnerability poses a significant risk to developers and users who may unknowingly install compromised packages.
Vulnerability Detail
The vulnerability in nabila-poke72 originates from its association with a campaign that floods the npm registry with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially leading to the installation of harmful code by unsuspecting users. The ramifications include compromised applications, data breaches, and a tarnished reputation for developers who inadvertently use these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nabila-poke72If 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, avoid using the nabila-poke72 package and consider using alternative packages that provide similar functionality without the associated risks. Always verify the integrity and source of packages before installation.
Conclusion
The discovery of malicious code in the nabila-poke72 package highlights the importance of vigilance when using open-source packages. Developers should regularly audit their dependencies and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can protect your applications from potential threats.
See every vulnerability recorded for nabila-poke72 →
FAQ
nabila-poke72 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
The vulnerability can lead to the installation of malicious code, which may compromise your application and data security.
You should uninstall the package immediately using npm uninstall nabila-poke72 and check for any other affected packages.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing package-lock.json files.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
