Critical Malicious Code Vulnerability in clob-utils-sdks Package

clob-utils-sdks Updated 20 Mar 2026

Summary

20/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1943: Malicious code in clob-utils-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 Your last release was probably never penetration tested 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-utils-sdks package is a utility library designed for developers using the npm ecosystem. It provides various functionalities that enhance the development process. However, this package has been identified as containing malicious code, which poses a significant risk to any system where it is installed.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the clob-utils-sdks package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information, including secrets and keys. The implications of this vulnerability are severe, as it can lead to full control of the affected system by an external entity. Users are advised to treat any system running this package as fully compromised.

How To Fix

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

npm uninstall clob-utils-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

Currently, there are no effective workarounds other than removing the package and securing your system. Ensure that you monitor your system for any unusual activity following the removal.

Conclusion

The clob-utils-sdks package has been identified as containing malicious code, posing a significant risk to any system where it is installed. Immediate action is required to remove the package and secure any sensitive information. Utilize tools like Vulert to monitor your applications for vulnerabilities effectively.

See every vulnerability recorded for clob-utils-sdks →

Share this vulnerability

FAQ

You should immediately remove the clob-utils-sdks package from your system and rotate any sensitive information stored on that system.

You can use the Vulert 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.

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

Vulert monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file, ensuring you 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-utils-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