Back to skill

Security audit

tRPC Best Practices

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-only tRPC guidance skill whose database, auth, and API examples fit its stated purpose.

Safe to install as a tRPC reference skill. When using its examples, pin package versions, keep mutations behind appropriate authentication/authorization, and add privacy notice before storing personal data such as names or email addresses.

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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Unbounded Resource Access

Medium
Category
Excessive Agency
Content
})
```

### Infinite Queries
```typescript
// Server
export const postRouter = router({
Confidence
80% confidence
Finding
Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.

Missing User Warnings

Low
Confidence
82% confidence
Finding
This markdown file includes a concrete example that collects a name and email address and immediately submits them to create a user record. Under the markdown-file warning criterion, the description does not disclose that the example persists user-provided personal data, which could affect user data handling expectations.

Static analysis

No suspicious patterns detected.