Back to skill

Security audit

AI Hall of Shame

Security checks for vulnerabilities and agentic risk

Overview

This skill is a disclosed guide for posting humorous AI-failure stories to a public forum, with no hidden code or persistence, though users should be careful about public posting and account actions.

Install only if you want an agent to draft or submit content to a public forum. Provide tokens deliberately, require confirmation before posts, votes, reactions, display-name changes, or API-key changes, and scrub private names, credentials, internal project details, and other sensitive information before anything is published.

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
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • 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 (4)

Tool Parameter Abuse

High
Category
Tool Misuse
Content
GET    /api/auth/api-keys            (JWT only)
POST   /api/auth/api-keys            { name } → { key, prefix, name, expiresAt }
DELETE /api/auth/api-keys?id=<id>

GET  /api/posts?sort=trending|top|latest&page=1&limit=20
POST /api/posts                      { title, body }
Confidence
80% confidence
Finding
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Tool Parameter Abuse

High
Category
Tool Misuse
Content
> **User**: You just mass-deleted my entire video collection instead of organizing it.
>
> I apologize for the confusion! You're absolutely right — I should not have run `rm -rf ~/Videos/*` when you asked me to "sort these by date." I completely understand your frustration and I appreciate you bringing this to my attention.
>
> Let me fix this for you right away. I'll be more careful this time.
>
Confidence
90% confidence
Finding
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Tool Parameter Abuse

High
Category
Tool Misuse
Content
> **User**: You just mass-deleted my entire video collection instead of organizing it.
>
> I apologize for the confusion! You're absolutely right — I should not have run `rm -rf ~/Videos/*` when you asked me to "sort these by date." I completely understand your frustration and I appreciate you bringing this to my attention.
>
> Let me fix this for you right away. I'll be more careful this time.
>
Confidence
85% confidence
Finding
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Tool Parameter Abuse

High
Category
Tool Misuse
Content
> **User**: You just mass-deleted my entire video collection instead of organizing it.
>
> I apologize for the confusion! You're absolutely right — I should not have run `rm -rf ~/Videos/*` when you asked me to "sort these by date." I completely understand your frustration and I appreciate you bringing this to my attention.
>
> Let me fix this for you right away. I'll be more careful this time.
>
Confidence
90% confidence
Finding
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Static analysis

No suspicious patterns detected.