Back to skill

Security audit

Secrets Vault

Security checks across malware telemetry and agentic risk

Overview

This appears to be a real local secrets vault, but it needs Review because it handles credentials while documenting risky secret export/sharing features that are not included for review.

Review carefully before installing. Use a strong unique master password, avoid putting real secrets on command lines, avoid plaintext .env export unless strictly necessary, do not sync or commit session/share/decrypted files, and do not rely on the advertised sharing, injection, or audit features unless their code is supplied and reviewed.

SkillSpector

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

Context-Inappropriate Capability

Medium
Confidence
91% confidence
Finding
The vault automatically pulls the master password from an environment variable or an arbitrary file path specified by another environment variable. In a secrets-management tool, this expands the trust boundary to ambient process state and filesystem content, making unintended password disclosure, misuse, or secret-source confusion more likely without explicit user consent.

Missing User Warnings

Medium
Confidence
97% confidence
Finding
The documentation instructs users to generate a `.env` file containing decrypted secrets in plaintext, but does not clearly warn that this writes sensitive credentials to disk where they may be read by other processes, editors, backups, sync tools, or accidentally committed to version control. In the context of a secrets vault, normalizing plaintext export materially weakens the protection boundary the vault is supposed to provide.

Missing User Warnings

Medium
Confidence
88% confidence
Finding
Exporting secrets into the shell environment can expose them through child processes, debug tooling, shell history patterns, crash dumps, process inspection on some systems, or accidental logging. The README presents environment injection as a convenience feature without adequately warning users about these exposure paths or constraining usage to short-lived trusted processes.

Missing User Warnings

Medium
Confidence
87% confidence
Finding
The code accesses sensitive credential sources silently, including environment variables and a file path controlled by an environment variable, without warning the user. In a vault tool, hidden fallback reads can cause operators to unknowingly rely on exposed secrets or read secrets from unexpected locations, increasing the chance of accidental disclosure and unsafe automation.

Missing User Warnings

Medium
Confidence
84% confidence
Finding
Secret deletion is irreversible and occurs immediately with no confirmation prompt, dry-run, or recovery mechanism. In a secrets vault, accidental deletion can cause credential loss, service disruption, and operational outages, especially when used interactively or from scripts with incorrect parameters.

Env Variable Harvesting

High
Category
Data Exfiltration
Content
if password:
            return password

        password_file = os.environ.get('SECRETS_VAULT_PASSWORD_FILE')
        if password_file and os.path.exists(password_file):
            with open(password_file, 'r') as f:
                return f.read().strip()
Confidence
89% confidence
Finding
os.environ.get('SECRETS_VAULT_PASSWORD

VirusTotal

63/63 vendors flagged this skill as clean.

View on VirusTotal