Malicious Code Injection in nabila-poke55: A Threat to npm Ecosystem
Summary
MAL-2025-161255: Malicious code in nabila-poke55 (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
nabila-poke55 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish itself under various names, thereby compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in nabila-poke55 originates from its design to include autopublish scripts that alter package.json files by removing private flags and changing version numbers. This allows the package to generate random names, often themed around Indonesian culture, and continuously republish itself, leading to pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly install these malicious packages, as they may inadvertently expose their applications to further vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nabila-poke55If 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 prevent the installation of malicious packages by using npm audit to identify vulnerabilities in your dependencies. Additionally, consider using a tool like Vulert to monitor your package-lock.json for real-time alerts on open-source vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The nabila-poke55 package presents a significant security threat within the npm ecosystem due to its malicious code designed to manipulate package files and republish itself. It is essential for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to safeguard their applications against such vulnerabilities.
See every vulnerability recorded for nabila-poke55 →
FAQ
nabila-poke55 is an npm package that has been identified as part of a malicious campaign designed to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability allows the package to modify critical files in your project, potentially leading to security risks and the pollution of the npm registry with malicious packages.
You should immediately uninstall the package using the command 'npm uninstall nabila-poke55' and check your project for any other potentially malicious packages.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Regularly audit your dependencies using 'npm audit' and stay updated on security advisories related to the packages you use. Consider implementing automated monitoring tools like Vulert.
