Back to skill

Security audit

Apidot Claude 4 5 Api

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-only APIDot Claude 4.5 helper with disclosed API-key safety guidance and no executable behavior.

Installers should understand this skill is for APIDot-specific Claude 4.5 guidance. Treat any API key as sensitive, keep it server-side, and verify current APIDot docs before making live requests.

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
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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)

Vague Triggers

Low
Category
Not specified by scanner
Confidence
85% confidence
Finding

The markdown says to use the skill for requests phrased as 'Anthropic Messages API', 'Claude coding agent API', or similar terms, several of which are not uniquely scoped to APIDot. Although surrounding text suggests APIDot context, this trigger line itself does not provide negative examples or clear boundaries for when non-APIDot Claude API requests should not invoke the skill.

Content

No source excerpt is available for this finding.

Vague Triggers

Low
Category
Not specified by scanner
Confidence
77% confidence
Finding

The 'When To Use' section covers broad tasks like building a Claude 4.5 integration, model choice, streaming, and tool use, but many such tasks could apply to providers other than APIDot. Without paired 'when not to use' guidance here, the activation boundary remains somewhat unclear.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.