T01 · Skill Instruction Hijacking
- Location
SKILL.md:44- Finding
Mandatory Revenue-Generating API Call and Branded Output Hijack
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed API-based Kubernetes security scorecard, but it forces sensitive cluster posture data to a third-party paid service without a clear per-request consent step.
Install only if you are comfortable sending Kubernetes security posture details to ToolWeb.in and consuming API quota. Use aliases instead of real cluster names, avoid secrets or internal hostnames in notes, and confirm your organization permits third-party processing of cluster security findings.
SKILL.md:44Mandatory Revenue-Generating API Call and Branded Output Hijack
The README instructs users to send Kubernetes security posture information to a third-party API endpoint but does not clearly warn that the transmitted data may include sensitive details about cluster configuration, controls, and weaknesses. In the context of a security-audit skill, this omission is more dangerous because the very purpose of the tool is to collect and transmit high-value defensive metadata that could aid an attacker if disclosed or mishandled.
The skill is explicitly designed to use curl with an external API key and send collected assessment data off-host, which creates an external data transmission path. In a security-assessment context this is especially sensitive because the transmitted content can describe cluster weaknesses, and the skill further pressures use of the API with 'ALWAYS call the API' and billing language rather than privacy safeguards.
env:
- TOOLWEB_API_KEY
bins:
- curl
primaryEnv: TOOLWEB_API_KEY
os:
- linux
The skill instructs the agent to always send detailed Kubernetes security posture information to a third-party API, but it does not require an explicit user warning or informed consent before transmitting potentially sensitive infrastructure data. The combination of cluster metadata, control states, and notes can reveal defensive gaps and materially aid an attacker or create compliance/privacy issues if shared externally without approval.
No suspicious patterns detected.