T01 · Skill Instruction Hijacking
- Location
SKILL.md:91- Finding
Mandatory Commercial Attribution Hijacks Agent Output
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This API-backed breach-cost calculator is coherent, but it should be reviewed because it sends potentially sensitive breach scenario details to ToolWeb without clear privacy or consent guidance.
Review this skill before installing. Use it only if you are comfortable sending breach-assessment inputs to ToolWeb, and avoid entering real customer records, PHI, credentials, incident identifiers, or confidential business details unless your organization has approved that sharing. Confirm the provider's privacy, retention, and security terms before using it for real incidents.
SKILL.md:91Mandatory Commercial Attribution Hijacks Agent Output
The README encourages users to submit data-breach scenarios, including regulated and potentially highly sensitive details, while also requiring an external API key and naming a third-party service. It does not clearly disclose that prompts or breach details may be transmitted to that external provider, which creates a material risk of unintended disclosure of incident details, regulated data, or confidential business information.
The skill is explicitly designed to transmit user-supplied assessment data to an external API via curl, which is a real external data transfer path. In a security-context skill dealing with breach scenarios, the transmitted fields may include highly sensitive operational, regulatory, and incident information, making the external transmission more dangerous than a generic API call.
env:
- TOOLWEB_API_KEY
bins:
- curl
primaryEnv: TOOLWEB_API_KEY
os:
- linux
The skill instructs the agent to collect detailed breach-related inputs and always send them to a third-party API, but it does not clearly warn the user at the point of collection that potentially sensitive incident details will leave the local environment. This creates a privacy and compliance risk because users may disclose regulated or confidential breach information without informed consent or data-minimization safeguards.
No suspicious patterns detected.