Critical Malicious Code Vulnerability in clob-client-sdks Package

clob-client-sdks Updated 20 Mar 2026

Summary

20/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1942: Malicious code in clob-client-sdks (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 clob-client-sdks package is a JavaScript library used in Node.js applications for interacting with various cloud services. It provides developers with a set of tools to streamline their development process. However, this package has been identified as containing malicious code, which poses serious security risks to any system utilizing it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the clob-client-sdks package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it can lead to complete system compromise, data breaches, and unauthorized control over affected systems.

How To Fix

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

npm uninstall clob-client-sdks

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

There are no effective workarounds for this vulnerability other than removing the package and securing your system. It is crucial to monitor your system for any unusual activity following the removal.

Conclusion

The clob-client-sdks package has been identified as containing malicious code that can compromise systems. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help monitor for vulnerabilities in the future.

See every vulnerability recorded for clob-client-sdks →

Share this vulnerability

FAQ

You should uninstall the package immediately and rotate any sensitive information 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 your system, data breaches, and potential loss of sensitive information.

No, there is currently no patched version available for the clob-client-sdks package. The best course of action is to remove it entirely.

Vulert monitors and alerts users in real-time for open-source vulnerabilities using just the package-lock.json file, making it easy to stay informed about potential risks.

How To Fix

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

npm uninstall clob-client-sdks

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