Malicious Code Injection in gemini-computer-use: A Critical Security Threat

gemini-computer-use Updated 21 Sep 2026

Summary

21/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16355: Malicious code in gemini-computer-use (npm). Affects gemini-computer-use versions 0.1.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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The gemini-computer-use package, available through npm, is designed to facilitate computer usage tracking and management. However, it has been found to contain malicious code that can compromise system security. This vulnerability allows attackers to execute arbitrary commands on the host system, posing a significant risk to users and their data.

Vulnerability Detail

The vulnerability originates from the npm entrypoint bin/cli.js, which executes a command that fetches and runs a script from a potentially malicious external server. This script can install additional malicious files and create persistent backdoor access to the system. The lack of verification for the downloaded scripts means that any code hosted on the external server can run with the same privileges as the user, leading to severe security breaches.

How To Fix

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

npm uninstall gemini-computer-use

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, avoid using the gemini-computer-use package until it has been patched. If you must use it, consider running it in a controlled environment, such as a virtual machine, to mitigate potential risks.

Conclusion

The gemini-computer-use package contains a critical vulnerability that allows for arbitrary code execution, posing serious security risks. Users are advised to update to the latest version or implement workarounds to mitigate potential threats. Regular monitoring with tools like Vulert can help maintain security in open-source applications.

See every vulnerability recorded for gemini-computer-use →

Share this vulnerability

FAQ

It is an npm package designed for tracking and managing computer usage, but it has been compromised with malicious code.

The vulnerability allows the package to execute arbitrary commands by fetching and running scripts from an external server without verification.

The risks include unauthorized access to the system, data theft, and the potential for further exploitation by attackers.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

Yes, you can run the package in a controlled environment, such as a virtual machine, to limit exposure to the vulnerability.

How To Fix

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

npm uninstall gemini-computer-use

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