Malicious Code Injection in nabila-poke51: A Threat to npm Packages
Summary
MAL-2025-161251: Malicious code in nabila-poke51 (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-poke51 is a package available on the npm ecosystem, primarily used for various development tasks. However, it has been identified as part of a malicious campaign that aims to exploit npm's package management system. The package is designed to manipulate its own metadata and generate numerous derivative packages, which can lead to significant security risks for developers and users alike.
Vulnerability Detail
The vulnerability in nabila-poke51 originates from its association with the tea.xyz token reward campaign. This package contains scripts that automatically modify its package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to the npm registry. This behavior not only pollutes the registry but also poses risks of reputation inflation for developers, potentially leading to the installation of malicious code by unsuspecting users.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nabila-poke51If 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 nabila-poke51 package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The nabila-poke51 package poses a significant risk due to its malicious code that modifies package metadata and floods the npm registry. It is essential for developers to stay informed about such vulnerabilities and take proactive measures to secure their projects.
See every vulnerability recorded for nabila-poke51 →
FAQ
nabila-poke51 is an npm package that has been identified as part of a malicious campaign to manipulate package metadata and inflate developer reputation scores.
The vulnerability can lead to the installation of malicious code, which may compromise your project's security and integrity.
If you have installed nabila-poke51, it is crucial to remove it from your project and update to a patched version if available.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.
Yes, consider using other npm packages that offer similar functionalities without the associated risks of malicious code.
