Github Cli

Security checks across malware telemetry and agentic risk

Overview

This is a documentation-only GitHub CLI reference whose powerful examples are expected for the tool but require care with tokens, secrets, extensions, and destructive commands.

Install only if you want an agent to reference GitHub CLI commands. Keep `gh` authenticated with the minimum scopes needed, confirm repo names before mutating or deleting anything, do not print or paste tokens, review `.env` files before importing them, and install `gh` extensions only from trusted repositories.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (4)

Missing User Warnings

Medium
Confidence
96% confidence
Finding
This section documents commands that directly reveal authentication material, including `gh auth status --show-token` and `gh auth token`, without a nearby warning that the token may be exposed in terminal history, logs, screenshots, shell pipelines, or copied outputs. In a reference skill intended for broad reuse, omission of that warning materially increases the chance of accidental credential disclosure.

Missing User Warnings

Medium
Confidence
94% confidence
Finding
The skill explains how to set GitHub secrets and plaintext variables, including bulk import from `.env`, but does not clearly distinguish encrypted secrets from plaintext variables or warn that `.env` files commonly contain sensitive credentials. That omission can lead users to upload secrets into plaintext variables, commit sensitive files, or mishandle local credential material.

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The Extensions section recommends searching, installing, upgrading, and executing third-party `gh` extensions without warning that extensions are external code fetched from repositories and run with the user's local permissions and GitHub credentials available to the CLI environment. This creates a realistic supply-chain and credential-theft risk if users install untrusted extensions.

Credential Access

High
Category
Privilege Escalation
Content
gh variable set MY_VAR --env staging --body "value"
gh variable set MY_VAR --org my-org --visibility all --body "value"

# Bulk set from .env file
gh variable set -f .env

# Get
Confidence
89% confidence
Finding
.env

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal