Malicious Code Injection in nabila-poke46: A Threat to npm Ecosystem

nabila-poke46 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161245: Malicious code in nabila-poke46 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

nabila-poke46 is a package within the npm ecosystem, which is often used for JavaScript development. This package is part of a broader campaign that exploits npm's publishing capabilities to inflate developer reputation scores through the automatic generation of derivative packages. The malicious nature of this package poses significant risks to developers and users alike, as it can lead to the proliferation of harmful software in the npm registry.

Vulnerability Detail

The vulnerability in nabila-poke46 originates from its association with the tea.xyz token reward campaign, which utilizes autopublish scripts to create and publish numerous derivative packages with randomized names. This malicious behavior modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, thereby polluting the npm registry. The ramifications of this vulnerability include potential security risks for applications relying on these packages, as well as damage to the integrity of the npm ecosystem.

How To Fix

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

npm uninstall nabila-poke46

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-poke46 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.

Conclusion

The nabila-poke46 package poses a significant threat due to its malicious code and association with a harmful campaign. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications and the npm ecosystem.

See every vulnerability recorded for nabila-poke46 →

Share this vulnerability

FAQ

nabila-poke46 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising security and functionality.

You should remove the package from your project immediately and check for any alternative packages that do not pose security risks.

You can use Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities. You can also check your application using the Vulert playground without any signup.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about vulnerabilities in the packages you use.

How To Fix

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

npm uninstall nabila-poke46

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