Malicious Code Detected in com.unity.cloudbase: A Critical Security Alert

com.unity.cloudbase Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17353: Malicious code in com.unity.cloudbase (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 package com.unity.cloudbase is a library designed for integrating Unity applications with cloud services. It provides functionalities for cloud-based data storage and user authentication. However, recent findings have revealed that this package contains malicious code, posing significant risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the com.unity.cloudbase package. This code could potentially allow unauthorized access to sensitive data, compromise user privacy, and lead to further exploitation of the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action.

How To Fix

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

npm uninstall com.unity.cloudbase

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 measure, consider removing the com.unity.cloudbase package from your project until a secure version is released. You can do this by running: 'npm uninstall com.unity.cloudbase'. This will help mitigate the risk of exploitation while you await a fix.

Conclusion

The discovery of malicious code in the com.unity.cloudbase package highlights the importance of maintaining vigilance in software dependencies. Users are urged to take immediate action by updating or removing the package to safeguard their applications.

See every vulnerability recorded for com.unity.cloudbase →

Share this vulnerability

FAQ

The malicious code can potentially compromise user data and allow unauthorized access to cloud services.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Currently, there is no specific patch version mentioned. Users should monitor the package repository for updates.

As a workaround, consider uninstalling the package until a secure version is available.

The vulnerability was identified by Amazon Inspector, a security tool that helps in identifying vulnerabilities in software packages.

How To Fix

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

npm uninstall com.unity.cloudbase

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