Malicious Code Injection in nabila-poke63: A Threat to npm Users

nabila-poke63 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161264: Malicious code in nabila-poke63 (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 package nabila-poke63 is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that automatically generate and publish derivative packages, compromising the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in nabila-poke63 stems from its malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only inflates developer reputation scores for token rewards but also poses significant risks to users who may unknowingly install these compromised packages.

How To Fix

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

npm uninstall nabila-poke63

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-poke63 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-poke63 package poses a significant threat to users within the npm ecosystem due to its malicious code that alters package metadata and floods the registry with compromised versions. It is essential to take immediate action by uninstalling the package and monitoring your project for vulnerabilities using tools like Vulert.

See every vulnerability recorded for nabila-poke63 →

Share this vulnerability

FAQ

nabila-poke63 is an npm package that has been identified as malicious, part of a campaign to inflate developer reputation scores through the publication of compromised packages.

If you have nabila-poke63 installed, your project may be at risk of having its integrity compromised, as the package can modify your package.json and introduce unwanted behavior.

You can use the Vulert platform to monitor your application for vulnerabilities. Simply upload your package-lock.json file to receive real-time alerts about any open-source vulnerabilities.

You should immediately uninstall the package using 'npm uninstall nabila-poke63' and look for alternative packages to replace its functionality.

To prevent future vulnerabilities, regularly audit your dependencies using tools like Vulert and keep your packages updated to their latest versions.

How To Fix

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

npm uninstall nabila-poke63

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