Malicious Code Injection in nabila-poke8 Package

nabila-poke8 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161282: Malicious code in nabila-poke8 (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The nabila-poke8 package 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 of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry and inflate developer reputation scores through automated scripts.

Vulnerability Detail

The vulnerability in the nabila-poke8 package stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file to remove private flags, change version numbers, and generate random names, leading to pollution of the npm registry. This can have serious ramifications, including the potential for developers to unknowingly install compromised packages, leading to security breaches in their applications.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall nabila-poke8

If 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-poke8 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to uninstall the package: 'npm uninstall nabila-poke8'.

Conclusion

The nabila-poke8 package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your software.

See every vulnerability recorded for nabila-poke8 →

Share this vulnerability

FAQ

The nabila-poke8 package is an npm package used in JavaScript development, but it has been identified as malicious.

This vulnerability can lead to the installation of compromised packages, which may introduce security risks and affect the integrity of your application.

You should uninstall the nabila-poke8 package immediately and monitor your application for any unusual behavior.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall nabila-poke8

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback