Critical Malicious Code Vulnerability in dpsdatahub (npm)

dpsdatahub Updated 02 Oct 2025

Summary

24/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6233: Malicious code in dpsdatahub (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

dpsdatahub is an npm package designed for data management and integration tasks. It allows developers to easily connect and manipulate data from various sources. However, this package has been compromised, embedding malicious code that poses significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the dpsdatahub package. This code can fully compromise any computer that has the package installed or running, potentially allowing unauthorized access to sensitive information, including secrets and keys. The malicious nature of the code is classified under CWE-506, indicating that it appears to be intentionally harmful. Users should be aware that simply removing the package may not eliminate all traces of the malicious software.

How To Fix

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

npm uninstall dpsdatahub

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

Currently, there are no effective workarounds other than removing the package entirely. Users should ensure that their systems are secure and monitor for any unusual activity following the removal.

Conclusion

The dpsdatahub package has been identified as containing malicious code that poses severe security risks. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for dpsdatahub →

Share this vulnerability

FAQ

You should remove the dpsdatahub package immediately and rotate any secrets or keys stored on the affected system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Failing to address this vulnerability can lead to unauthorized access to sensitive data and complete control of your system by malicious actors.

Currently, there is no patched version available. The best course of action is to remove the package.

Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software, providing an easy way to stay informed.

How To Fix

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

npm uninstall dpsdatahub

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