Back to skill

Security audit

Skills

Security checks for vulnerabilities and agentic risk

Overview

The scanners report a transcript skill with disclosed connection and credential setup guidance; the verdict is benign, with medium confidence and one credential-related alert assessed as expected for its purpose.

The available results support a benign verdict, but the scan is marked partial: it could not resolve local references named in the skill guidance. Consider whether you are comfortable connecting to the stated service and granting its requested authorization, and keep credentials in your client’s secure configuration. The verdict is not a guarantee that the skill is risk-free.

Vulnerability Patterns
  • 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
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · SKILL.md (reported line 14)May include surrounding context.

md
Use an existing ProClipper connection when available. Otherwise, configure `https://proclipper.app/mcp` as a remote Streamable HTTP MCP server in a compatible assistant. Complete the provider's OAuth sign-in and consent flow. Connections can be revoked at `https://proclipper.app/dashboard/connections`.

For clients supporting custom headers, an API key from `https://proclipper.app/dashboard/api-keys` can be supplied as `Authorization: Bearer <key>`. Keep credentials in the client's secure configuration, never in URLs, this skill, or generated answers. OAuth access tokens authorize MCP only; REST requires an API key. Client compatibility must be checked rather than assumed.

## Retrieve transcripts