Back to skill

Security audit

1.2.0

Security checks for vulnerabilities and agentic risk

Overview

This skill is a lightweight release checklist/template helper with only inert version and healthcheck scripts, despite a small naming inconsistency.

Before installing, treat this as a checklist/template skill rather than a full release automation toolkit. Verify any referenced release commands exist in your own environment before relying on them during a deploy window.

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
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • 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)

Tp4

High
Category
MCP Tool Poisoning
Confidence
97% confidence
Finding

The declared description suggests functional helpers for coordinating release-day activities. The supplied code does not implement any such operational behavior; it only echoes a version identifier. While version reporting could be a minor supporting utility within a larger toolkit, this code chunk by itself does not match the declared primary purpose. Therefore, this chunk is a description-behavior mismatch.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
98% confidence
Finding

There is a clear description-behavior mismatch. The declared purpose suggests functionality related to release-day operations and readiness workflows, but the code only outputs a fixed "ok" message with a name/version string. This looks like a minimal healthcheck script rather than a release coordination helper. No special resource access or triggers are present, but the primary purpose does not align with the description.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.