Malicious Code Detected in asset_cloud Package - MAL-2025-14943

asset_cloud Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14943: Malicious code in asset_cloud (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 asset_cloud package is an npm library designed for cloud asset management, providing functionalities for tracking and managing cloud resources. However, it has been identified to contain malicious code, posing significant risks to users who integrate it into their applications. The presence of such code can lead to unauthorized access, data breaches, and other security vulnerabilities.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the asset_cloud package. This code can execute harmful actions without the user's consent, potentially compromising sensitive data and system integrity. The malicious nature of this code was confirmed by security researchers, raising alarms about the safety of using this package in production environments.

How To Fix

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

npm uninstall asset_cloud

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 using alternative packages that provide similar functionalities without the associated risks. Additionally, you can monitor your application for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for real-time alerts on open-source vulnerabilities.

Conclusion

The asset_cloud package has been identified as containing malicious code, which poses a serious risk to users. It is crucial to remove this package from your projects and monitor for any updates or patches. Utilizing tools like Vulert can help maintain the security of your applications by providing real-time vulnerability alerts.

See every vulnerability recorded for asset_cloud →

Share this vulnerability

FAQ

The asset_cloud package is an npm library used for managing and tracking cloud assets.

The malicious code can execute unauthorized actions, potentially leading to data breaches and system compromises.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

You should remove the asset_cloud package from your project and look for a secure alternative.

Regularly check the package repository for updates and consider using tools like Vulert to monitor your dependencies for vulnerabilities.

How To Fix

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

npm uninstall asset_cloud

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