Critical Vulnerability in Cloudcarl: Malicious Code Detected

cloudcarl Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17178: Malicious code in cloudcarl (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

Cloudcarl is an npm package designed for cloud-related functionalities, offering various tools and utilities for developers. However, it has been identified to contain malicious code, posing significant security risks to applications that utilize it. This vulnerability can lead to unauthorized access, data breaches, and other malicious activities.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the cloudcarl package, which was introduced in version 0 and has persisted in subsequent releases. This malicious code can compromise the integrity of applications using the package, potentially leading to severe security breaches, data loss, and unauthorized access to sensitive information.

How To Fix

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

npm uninstall cloudcarl

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, consider replacing the cloudcarl package with an alternative package that provides similar functionalities without the associated risks. Review your project's dependencies and ensure that no other packages are relying on cloudcarl.

Conclusion

The discovery of malicious code in the cloudcarl npm package poses a significant threat to applications utilizing it. It is crucial for developers to take immediate action by removing the package and monitoring their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.

See every vulnerability recorded for cloudcarl →

Share this vulnerability

FAQ

The malicious code is designed to exploit vulnerabilities in applications, potentially leading to unauthorized access and data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By simply analyzing your package-lock.json file, Vulert can help identify if your application is affected.

The best mitigation strategy is to remove the cloudcarl package and replace it with a secure alternative. Regularly monitor your dependencies for vulnerabilities.

If immediate removal is not possible, ensure that your application has robust security measures in place, such as firewalls and intrusion detection systems, to minimize potential risks.

Detailed information about the vulnerability can be found on the GitHub repository of the malicious packages project, specifically at the link provided in the vulnerability details.

How To Fix

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

npm uninstall cloudcarl

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