Critical Malicious Code Vulnerability in cloude-code Package

cloude-code Updated 20 Feb 2026

Summary

20/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-954: Malicious code in cloude-code (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The cloude-code package is a Node.js library designed for cloud-based development, providing tools and utilities for developers to streamline their workflows. However, it has been identified as containing malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk to users, as it can lead to unauthorized access and data breaches.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the cloude-code package, identified under the alias GHSA-8vcq-w335-fh83. Any system running this package is considered fully compromised, as it may allow external entities to gain control over the system. This can result in the exposure of sensitive information, including secrets and keys stored on the affected computer. The malicious code is embedded within the package, making it difficult to detect and remove completely.

How To Fix

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

npm uninstall cloude-code

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 to mitigate the risks posed by this vulnerability other than removing the package and securing your system.

Conclusion

The cloude-code package contains malicious code that poses a severe security risk to any system where it is installed. Immediate action is required to remove the package and secure sensitive information. Users should remain vigilant and utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for cloude-code →

Share this vulnerability

FAQ

You should remove the cloude-code 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.

After removing the package, ensure that you rotate all secrets and keys. However, be aware that full recovery may not be guaranteed due to potential lingering malicious software.

Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

If a patched version is released, updating the package will help. However, it is essential to remove the existing compromised version first.

How To Fix

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

npm uninstall cloude-code

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