Critical Malicious Code Vulnerability in cloud-binary Package

cloud-binary Updated 02 Oct 2025

Summary

15/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5901: Malicious code in cloud-binary (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 cloud-binary package is an npm library designed for handling binary data in cloud environments. It provides functionalities for uploading, downloading, and managing binary files efficiently. However, this package has been identified to contain malicious code that compromises the security of any system it is installed on, making it a significant risk for developers and organizations relying on it.

Vulnerability Detail

The vulnerability originates from the inclusion of embedded malicious code within the cloud-binary package. This code can lead to complete system compromise, allowing unauthorized access to sensitive data and system controls. The malicious nature of this code means that any computer running this package should be considered fully compromised, necessitating immediate action to mitigate potential damage.

How To Fix

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

npm uninstall cloud-binary

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 the malicious code in the cloud-binary package. The best course of action is to remove the package entirely and secure the system.

Conclusion

The cloud-binary package has been identified as containing malicious code that poses a significant risk to any system it is installed on. Immediate removal of the package and rotation of sensitive credentials are essential steps to mitigate the impact of this vulnerability.

See every vulnerability recorded for cloud-binary →

Share this vulnerability

FAQ

The cloud-binary package is an npm library used for managing binary data in cloud applications.

The malicious code can lead to full system compromise, allowing attackers to access sensitive data and control the system.

You should immediately remove the cloud-binary package and rotate any secrets or keys stored on the affected system.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Currently, there are no patches available for the cloud-binary package. The recommended action is to remove the package.

How To Fix

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

npm uninstall cloud-binary

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