Malicious Code Detected in dip-client Package - Security Alert

dip-client Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18464: Malicious code in dip-client (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 dip-client package is a Node.js library designed for client-side interactions with various APIs. It is commonly used in web applications to facilitate communication between the frontend and backend services. However, recent findings have revealed that this package contains malicious code, posing a significant security risk to applications that utilize it.

Vulnerability Detail

The vulnerability in the dip-client package originates from the inclusion of malicious code that can compromise the security of applications using this library. This code may allow unauthorized access to sensitive data, lead to data breaches, or facilitate further attacks on the system. The malicious nature of this code makes it imperative for developers to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall dip-client

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 remove the dip-client package from your project if it is not critical to your application's functionality. Use the command: npm uninstall dip-client. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the dip-client package poses a serious threat to applications that rely on it. Developers must take proactive measures to update or remove the package to safeguard their applications. Utilizing tools like Vulert can help monitor and alert for vulnerabilities in real-time, ensuring better security practices.

See every vulnerability recorded for dip-client →

Share this vulnerability

FAQ

The dip-client package is used for client-side API interactions in Node.js applications, facilitating communication between frontend and backend services.

You can check if your application is affected by this vulnerability using Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to analyze your package-lock.json without any signup.

Using the dip-client package with the malicious code can lead to unauthorized access to sensitive data, data breaches, and further attacks on your application.

Currently, there is no specific patched version mentioned. It is essential to keep an eye on updates from the package maintainers and update as soon as a patch is released.

If immediate updates are not possible, consider removing the dip-client package and using alternative libraries that do not have known vulnerabilities.

How To Fix

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

npm uninstall dip-client

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