Critical Malicious Code Vulnerability in dataglove Package

dataglove Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18000: Malicious code in dataglove (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The dataglove package is an npm library designed for various data manipulation tasks, providing users with tools to handle and process data efficiently. However, its recent discovery of malicious code poses significant risks to users, potentially compromising their applications and data integrity.

Vulnerability Detail

The vulnerability in the dataglove package stems from the inclusion of malicious code that can execute unauthorized actions within the user's environment. This code was introduced in version 0 and can lead to severe ramifications, including data theft, unauthorized access, and potential system compromise. Users of this package are at risk of having their applications manipulated or their data exposed to malicious actors.

How To Fix

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

npm uninstall dataglove

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 dataglove package from their project until a secure version is released. This can be done by executing the following command: npm uninstall dataglove.

Conclusion

The discovery of malicious code in the dataglove package poses a serious threat to users. It is crucial to take immediate action by updating or uninstalling the package to protect your applications and data. Utilize tools like Vulert to monitor for vulnerabilities effectively.

See every vulnerability recorded for dataglove →

Share this vulnerability

FAQ

The malicious code can execute unauthorized actions, potentially leading to data theft or system compromise.

You can use Vulert's playground to check if your application is affected by this vulnerability without any signup required. Visit Vulert Scanner for more information.

If you cannot update the package right away, consider uninstalling it as a temporary measure to mitigate risks.

Check the official npm repository or the package's GitHub page for any updates or patches that address the vulnerability.

Vulert uses package-lock.json to monitor and alert in real-time for open-source vulnerabilities in your software, providing a proactive approach to security.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall dataglove

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