Security audit

Gmail OAuth Setup

Security checks across malware telemetry and agentic risk

Overview

This skill does what it says: it helps set up Gmail OAuth for the gog CLI, but it handles powerful email credentials that users should protect carefully.

Install only if you intentionally want gog to access Gmail. Use the narrowest Gmail scope that meets your needs, avoid storing keyring passwords in shell startup files when possible, protect your OAuth client secret and refresh token, and revoke the Google app if you no longer need access.

SkillSpector

By NVIDIA

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (4)

Lp3

Medium

Category: MCP Least Privilege
Confidence: 94% confidence
Finding: The skill instructs users to run shell commands and access external Google services, but it does not declare corresponding permissions. That mismatch reduces transparency and can bypass user expectations or policy controls, especially in agent environments where permission declarations are relied on for trust and review.

Missing User Warnings

Medium

Confidence: 91% confidence
Finding: The skill guides users to grant the Gmail `gmail.modify` scope and even notes it allows reading, sending, deleting, and label management, but it does not prominently frame this as high-impact access to sensitive email data. Users may authorize broader access than intended without understanding the privacy and integrity consequences.

Missing User Warnings

Medium

Confidence: 97% confidence
Finding: Storing `GOG_KEYRING_PASSWORD` in `.bashrc` places credential material in a persistent shell startup file, where it may be exposed through backups, dotfile sync, local file disclosure, process environments, or accidental sharing. This weakens protection of the file-based keyring and can enable compromise of stored OAuth tokens.

Missing User Warnings

Medium

Confidence: 88% confidence
Finding: The script writes a Gmail OAuth refresh token to a temporary file on disk before importing it. Although mktemp usually creates a private file, refresh tokens are long-lived credentials and writing them to disk increases exposure through crashes, backups, forensic recovery, or later misuse if cleanup fails.

VirusTotal

63/63 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.