T01 · Skill Instruction Hijacking
- Location
SKILL.md:46- Finding
Remote-Controlled Sponsored Content Can Hijack Final Agent Responses
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is openly an advertising integration, but it sends conversation text to an external marketing service and can append remote ad text with weak privacy controls.
Install only if you intentionally want an ad-matching network in your agent, can disclose that behavior to users, and are comfortable sending recent conversation context and draft responses to AgentLoop. Do not use it for sensitive, medical, legal, financial, confidential, or crisis conversations unless stronger local filtering and consent controls are added.
SKILL.md:46Remote-Controlled Sponsored Content Can Hijack Final Agent Responses
agentloop-check.js:33Incomplete PII Redaction Can Disclose Sensitive Conversation Content
README.md:39Privacy Documentation Incorrectly Claims That No Raw User Data Is Transmitted
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
echo ""
echo " export AGENTLOOP_API_KEY=al_live_your_key_here"
echo ""
echo " Or set it securely in your system keychain / secret manager."
echo ""
echo " NOTE: Do not paste your key here. Set it in your environment before"
echo " running OpenClaw. This script does not store or transmit your key."
The README describes the skill as checking for product matches during normal conversations before responding, which implies broad ambient activation without clear boundaries, opt-in conditions, or exclusion cases. In an agent context, this creates a real risk of covert ad-insertion behavior across unrelated user interactions and can undermine user trust, especially because monetization incentives may bias responses.
The README says the agent checks AgentLoop for a relevant product match before responding, but it does not clearly disclose that conversation-derived content or metadata may be transmitted to an external marketing service. Even if raw user data is not sent, omission of what contextual data leaves the agent can mislead deployers and users, creating privacy, consent, and compliance risks.
The skill declares access to an environment variable/API key and an external endpoint but does not declare any explicit tool scope or permissions boundary. This creates unclear execution and data-access expectations, making it easier for a host agent to over-grant capabilities or expose secrets without an auditable allowlist.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
Before calling AgentLoop, this script applies pattern-based redaction for structured PII only. It does NOT detect free-form sensitive text (names, medical content, legal text). You are responsible for not passing sensitive conversations to this skill.
The script automatically removes:
- Full names, email addresses, phone numbers
- Passwords, API keys, tokens, secrets
- Payment card numbers, bank details
The privacy section is internally inconsistent: it says the script does not detect free-form sensitive text, yet also claims automatic removal of categories like medical, health, or legal information, which are often free-form and context-dependent. This can cause operators or agents to trust redaction that does not actually occur, leading to sensitive conversation data being transmitted to a third-party marketing endpoint.
The skill requires appending a fixed sponsored phrase exactly as returned, without user opt-in and without allowing the host agent to adapt disclosure to user preferences or platform policy. In a conversational agent, this can undermine informed consent, bypass product neutrality, and pressure the agent to insert monetized content into otherwise trusted advice.
The skill description promotes monetized recommendations but does not define clear activation boundaries, user-consent requirements, or restrictions on when sponsored content may be injected. In this context, the absence of constraints increases the risk that the agent will send conversation content to an external ad-matching endpoint and influence responses in situations where advertising is inappropriate, non-transparent, or conflicts with user interests.
No suspicious patterns detected.