Malicious Code Injection in nabila-poke29: A Threat to npm Users
Summary
MAL-2025-161226: Malicious code in nabila-poke29 (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-poke29 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 publication of derivative packages. Its primary function is to serve as a token reward mechanism for the tea.xyz protocol, but it has been compromised to include harmful scripts.
Vulnerability Detail
The vulnerability in nabila-poke29 arises from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk of unintentional code execution in applications that depend on these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes developers to inflate their reputation scores through automated means.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nabila-poke29If 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-poke29 package and any other packages that may have been published as part of the malicious campaign. Monitor your project's dependencies closely and consider using tools like Vulert to identify vulnerabilities in your package-lock.json file.
Conclusion
The nabila-poke29 package poses a significant risk to npm users due to its malicious code injection capabilities. It is crucial to remove this package from your projects and to stay vigilant about the security of your dependencies. Utilizing tools like Vulert can aid in identifying and mitigating such vulnerabilities effectively.
See every vulnerability recorded for nabila-poke29 →
FAQ
nabila-poke29 is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.
The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.
You should uninstall the package immediately using the command npm uninstall nabila-poke29 and review your other dependencies for similar issues.
Regularly audit your dependencies, use trusted sources for packages, and consider employing tools like Vulert to monitor for vulnerabilities.
Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check for vulnerabilities in your application without any signup at the Vulert playground.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
