Critical Malicious Code Vulnerability in cli-wasm Package

cli-wasm Updated 02 Oct 2025

Summary

09/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5677: Malicious code in cli-wasm (npm). Affects cli-wasm versions 0.0.1 – 2.2.2. 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 cli-wasm package is a tool designed for executing WebAssembly modules in command-line environments. It allows developers to leverage the performance benefits of WebAssembly in various applications. However, this package has been found to contain embedded malicious code, posing significant security risks to users who install it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the cli-wasm package. Any computer that has this package installed is considered fully compromised, meaning that all secrets and keys stored on that computer should be rotated immediately from a different machine. The malicious code can potentially allow unauthorized access and control over the affected system, leading to data breaches and further exploitation.

How To Fix

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

npm uninstall cli-wasm

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 workaround, you can temporarily avoid using the cli-wasm package and explore alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your system's security measures are up to date.

Conclusion

The cli-wasm package has been identified as containing malicious code, posing serious security risks to users. Immediate action is required to remove the package and secure any sensitive information. Regular monitoring of dependencies and using tools like Vulert can help prevent future vulnerabilities.

See every vulnerability recorded for cli-wasm →

Share this vulnerability

FAQ

You should immediately uninstall the cli-wasm package and rotate any sensitive information stored on your system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated to the latest secure versions.

Ignoring this vulnerability can lead to unauthorized access to your system, data breaches, and potential exploitation by malicious actors.

You can find detailed information about the cli-wasm vulnerability on its GitHub repository and security advisories related to it.

How To Fix

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

npm uninstall cli-wasm

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