Ravi secrets

Security checks across malware telemetry and agentic risk

Overview

This is a straightforward Ravi secret-manager skill that intentionally stores, retrieves, lists, and deletes API keys or tokens, with sensitive but disclosed behavior.

Install this only if you trust the Ravi CLI and service with API keys or tokens. Prefer least-privilege credentials, retrieve only specific secrets when needed, avoid printing or logging secret values, and carefully verify UUIDs before deleting secrets.

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 (2)

Missing User Warnings

Medium

Confidence: 91% confidence
Finding: The skill explicitly documents commands that return plaintext secret values and even encourages piping them through shell tools, but it does not warn that terminal history, logs, process inspection, shell tracing, and copied command output can expose those secrets. In a secrets-management skill, this omission increases the chance that users will inadvertently leak sensitive credentials while following the examples.

Missing User Warnings

Medium

Confidence: 84% confidence
Finding: The documentation presents `ravi secrets delete <uuid>` as a simple command without stating that deletion is irreversible or advising users to verify the target first. For a secrets store, accidental deletion can disrupt production systems, break automations, and cause loss of recovery material if the secret is not backed up elsewhere.

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal