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

nabila-poke75 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161277: Malicious code in nabila-poke75 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

nabila-poke75 is an npm package that appears to be part of a broader malicious campaign targeting the npm registry. This package is designed to exploit the npm ecosystem by generating and publishing derivative packages with randomized names, thereby inflating developer reputation scores for token rewards. Its functionality is compromised, making it a potential threat to users and developers relying on npm packages.

Vulnerability Detail

The vulnerability in nabila-poke75 originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of the packages within it. Users of this package may unknowingly expose their applications to security risks and instability.

How To Fix

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

npm uninstall nabila-poke75

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 measure, avoid using the nabila-poke75 package and monitor your project's dependencies for any signs of malicious activity. Regularly audit your npm packages using tools like npm audit or Vulert to identify vulnerabilities.

Conclusion

The nabila-poke75 package poses a significant threat to the npm ecosystem due to its malicious behavior. It is essential for developers to be vigilant and remove any instances of this package from their projects. Regular monitoring and auditing of dependencies can help maintain the security and integrity of applications.

See every vulnerability recorded for nabila-poke75 →

Share this vulnerability

FAQ

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

The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and stability.

You should uninstall the package immediately using the command npm uninstall nabila-poke75 and check for any other affected packages.

You can use tools like npm audit or Vulert to monitor your project's dependencies for known vulnerabilities and receive real-time alerts.

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

How To Fix

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

npm uninstall nabila-poke75

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