T01 · Skill Instruction Hijacking
- Location
SKILL.md:34- Finding
Mandatory Commercial API Use Hijacks Agent Behavior and Output
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This security-scanner skill is purpose-aligned, but it requires sending detailed agent security architecture to a paid third-party API without a clear consent, redaction, or privacy step.
Only install this if you are comfortable sending your agent's architecture, tools, authentication approach, credential-handling description, deployment details, and security controls to ToolWeb. Do not include actual secrets, tokens, hostnames, customer data, or private implementation details unless you have reviewed ToolWeb's privacy and retention terms and have approval to share that information.
SKILL.md:34Mandatory Commercial API Use Hijacks Agent Behavior and Output
SKILL.md:60Security-Sensitive Architecture Data Is Sent to an External Service Without a Consent or Redaction Step
The README requires a third-party API key and presents the skill as an agent security scanner, but it does not disclose whether agent prompts, architecture details, tool inventories, or secrets-adjacent context may be transmitted to an external service. In a security-auditing context, users are especially likely to submit sensitive operational details, so omission of data handling and transmission warnings creates a real confidentiality risk.
The skill explicitly tells the agent to gather sensitive security-relevant metadata such as authentication mechanisms, token handling, access controls, and architecture details, then send the full scan payload to an external endpoint. This creates a concentrated disclosure of defensive configuration data that could materially aid an attacker or leak confidential internal design information if mishandled, intercepted, or stored insecurely by the third party.
The skill directs collection and transmission of detailed agent architecture and security posture data to a third-party API, but it does not require an explicit user-facing disclosure or consent step before exfiltration. Even if the service is legitimate, these details can expose attack surface, auth design, token handling practices, and deployment weaknesses that are sensitive from a defensive security standpoint.
The skill contains a direct external transmission instruction using curl to POST user-supplied agent data and an API key to a remote service. External transmission is not inherently malicious, but in this context it is security-sensitive because the payload contains internal architecture and authentication information, and the skill strongly mandates using the remote service instead of local analysis.
curl -s -X POST "https://portal.toolweb.in/apis/security/agentvulnly" \
-H "Content-Type: application/json" \
-H "X-API-Key: $TOOLWEB_API_KEY" \
-d '{