Back to skill

Security audit

Keyapi Google

Security checks across malware telemetry and agentic risk

Overview

This skill coherently provides KeyAPI-backed Google search workflows, with credential-handling caveats users should understand before setup.

Install only if you are comfortable giving the skill a KeyAPI token and having that token stored in your shell profile. Prefer running setup in a private terminal, avoid the --token command on shared systems, and review or remove the managed KEYAPI_TOKEN block from your shell profile if you uninstall or rotate credentials.

SkillSpector

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

Missing User Warnings

Medium
Confidence
97% confidence
Finding
The script reads KEYAPI_TOKEN using readline.question(), which echoes the token to the terminal as the user types. This can expose the secret to shoulder-surfing, terminal recording/logging tools, or shared session history, and the script does not warn users that input will be visible. In this skill context, the script is specifically for API credential setup, so handling secrets safely is a core requirement and the issue is more significant than in non-sensitive input flows.

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

Detected: suspicious.env_credential_access, suspicious.secret_argv_exposure

Environment variable access combined with network send.

Critical
Code
suspicious.env_credential_access
Location
scripts/keyapi-api.mjs:127

Instructions pass high-value credentials through process argv.

Critical
Code
suspicious.secret_argv_exposure
Location
references/setup-and-auth.md:42