Security audit

Azure Keyvault Py

Security checks for vulnerabilities and agentic risk

Overview

The skill is a coherent Azure Key Vault SDK guide, but its examples can expose real secrets in logs and include permanent deletion without enough guardrails.

Review before installing or using this skill in production. Do not copy examples that print secret values; use retrieved secrets only in memory and redact logs. Treat purge examples as destructive operations requiring explicit approval, backups, and the correct vault context. Prefer pinned dependencies or a reviewed lock file when installing the Azure SDK packages.

A.I.G

Vulnerability Patterns

Insecure DependenciesIntroduces malicious components through unsafe dependency sources
Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review

Findings (2)

T08 · Insecure Dependencies

Warning

Location: SKILL.md:15
Finding: Unpinned Third-Party Azure SDK Dependencies
Content: View full analysis
Remediation: View remediation

T09 · Insecure Skill Coding Practices

Error

Location: SKILL.md:56
Finding: Key Vault Secret Values Printed in Plaintext
Content: View full analysis
Remediation: View remediation

SkillSpector

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

Category: Not specified by scanner
Confidence: 90% confidence
Finding: The examples retrieve and print secret values, and elsewhere note how to access certificate-backed secret material, without a privacy or logging warning. This can normalize exposing sensitive values to stdout, notebooks, CI logs, shells, or telemetry, leading to accidental credential disclosure even though the SDK itself is not insecure.
Content: No source excerpt is available for this finding.

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 96% confidence
Finding: The skill includes a purge example for a deleted secret without explicitly warning that purge is irreversible and can permanently destroy recoverable secret material. In a security-focused SDK skill, users may copy examples directly, so omission of a warning increases the chance of accidental destructive operations in production or during incident response.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.