Critical Malicious Code Vulnerability in dataops Package

dataops Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18004: Malicious code in dataops (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 dataops package is an npm library designed for data operations, providing functionalities that facilitate data manipulation and processing tasks. It is widely used in various applications for its ease of use and efficiency. However, the package has been found to contain malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the dataops package stems from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action.

How To Fix

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

npm uninstall dataops

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, users can remove the dataops package from their project until a secure version is released. This can be done using the command: 'npm uninstall dataops'. Consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The discovery of malicious code in the dataops package poses a serious threat to users and their applications. It is crucial to take immediate action by updating or removing the package until a secure version is released. Utilizing tools like Vulert can help in monitoring vulnerabilities effectively.

See every vulnerability recorded for dataops →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to sensitive data and compromise application security.

You can use Vulert, which monitors and alerts for open-source vulnerabilities. Simply upload your package-lock.json file to check for vulnerabilities.

Currently, there is no patched version available. Users should monitor the package repository for updates.

Consider removing the dataops package from your project and using alternative solutions until a secure version is released.

Vulert uses your package-lock.json file to monitor for vulnerabilities in real-time, providing alerts without requiring code access or installation.

How To Fix

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

npm uninstall dataops

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