Critical Malicious Code Vulnerability in gitbook-plugin-datadotworld

gitbook-plugin-datadotworld Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21478: Malicious code in gitbook-plugin-datadotworld (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

The gitbook-plugin-datadotworld is an npm package designed to integrate data from the Datadotworld platform into GitBook documentation. It allows users to seamlessly embed datasets and visualizations, enhancing the documentation experience. However, this package has been found to contain malicious code, posing a significant risk to users who implement it in their projects.

Vulnerability Detail

The vulnerability in gitbook-plugin-datadotworld originates from the inclusion of malicious code within the package. This code can potentially compromise user data, lead to unauthorized access, or execute harmful operations on the host system. The malicious nature of this code makes it imperative for users to take immediate action to mitigate risks associated with its use.

How To Fix

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

npm uninstall gitbook-plugin-datadotworld

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, users can remove the gitbook-plugin-datadotworld package from their project until a safe version is released. You can uninstall the package using the following command: npm uninstall gitbook-plugin-datadotworld.

Conclusion

The discovery of malicious code in the gitbook-plugin-datadotworld package highlights the importance of vigilance when using open-source software. Users must take immediate action to update or remove the package to protect their applications from potential threats.

See every vulnerability recorded for gitbook-plugin-datadotworld →

Share this vulnerability

FAQ

It is an npm package that allows users to integrate Datadotworld datasets into GitBook documentation.

The specific details of the malicious code have not been disclosed, but it poses risks such as unauthorized access and data compromise.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Users are advised to check the package repository for any updates or patches that address the vulnerability.

As a temporary measure, consider uninstalling the package until a safe version is available.

How To Fix

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

npm uninstall gitbook-plugin-datadotworld

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