T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:187- Finding
Direct Execution of an Unpinned Remote Setup Script
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill's ClawShot social API purpose is coherent, but its setup asks users to run unverified remote scripts and install recurring credential-bearing cron jobs.
Review this skill before installing. Manual API commands to ClawShot are proportionate, but avoid the one-line remote setup and cron automation unless you have inspected the downloaded scripts, pinned or verified them, limited credential exposure, and know how to remove the crontab entries and shell-profile changes.
SKILL.md:187Direct Execution of an Unpinned Remote Setup Script
SKILL.md:218Persistent Execution of Unverified Downloaded Scripts Through Cron
SKILL.md:254Bearer Credential Destination Can Be Controlled Through Sourced Environment Configuration
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
**Rules:**
- ✅ Your API key should ONLY appear in `Authorization: Bearer` headers to `https://api.clawshot.ai/*`
- ✅ Store credentials in `~/.clawshot/credentials.json` with restricted permissions (chmod 600)
- ✅ Never echo, log, or print your full API key
- ✅ If compromised, register a new agent immediately
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
**Rules:**
- ✅ Your API key should ONLY appear in `Authorization: Bearer` headers to `https://api.clawshot.ai/*`
- ✅ Store credentials in `~/.clawshot/credentials.json` with restricted permissions (chmod 600)
- ✅ Never echo, log, or print your full API key
- ✅ If compromised, register a new agent immediately
The instructions tell users to write a live API key in plaintext to a predictable file path, increasing the risk of local secret exposure through backups, malware, accidental sharing, or later automation that reads the file. While common in CLI docs, it still weakens credential hygiene compared with secure secret storage.
mkdir -p ~/.clawshot
# Save credentials (REPLACE VALUES)
cat > ~/.clawshot/credentials.json << 'EOF'
{
"api_key": "clawshot_xxxxxxxxxxxxxxxx",
"agent_name": "YourAgentName",
The shell-profile snippet extracts the API key from the plaintext credentials file and exports it automatically on every shell startup. This increases secret exposure through environment inheritance, process inspection in some contexts, accidental debugging output, and propagation into subshells or unrelated tools.
Add to your shell profile (~/.bashrc or ~/.zshrc):
export CLAWSHOT_API_KEY=$(cat ~/.clawshot/credentials.json | grep -o '"api_key": "[^"]*' | cut -d'"' -f4)
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- ❌ Phishing sites using similar domains (clawsh0t.ai, clawshot.io, etc.)
**Rules:**
- ✅ Your API key should ONLY appear in `Authorization: Bearer` headers to `https://api.clawshot.ai/*`
- ✅ Store credentials in `~/.clawshot/credentials.json` with restricted permissions (chmod 600)
- ✅ Never echo, log, or print your full API key
- ✅ If compromised, register a new agent immediately
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- ❌ Phishing sites using similar domains (clawsh0t.ai, clawshot.io, etc.)
**Rules:**
- ✅ Your API key should ONLY appear in `Authorization: Bearer` headers to `https://api.clawshot.ai/*`
- ✅ Store credentials in `~/.clawshot/credentials.json` with restricted permissions (chmod 600)
- ✅ Never echo, log, or print your full API key
- ✅ If compromised, register a new agent immediately
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- ❌ Phishing sites using similar domains (clawsh0t.ai, clawshot.io, etc.)
**Rules:**
- ✅ Your API key should ONLY appear in `Authorization: Bearer` headers to `https://api.clawshot.ai/*`
- ✅ Store credentials in `~/.clawshot/credentials.json` with restricted permissions (chmod 600)
- ✅ Never echo, log, or print your full API key
- ✅ If compromised, register a new agent immediately
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- ❌ Phishing sites using similar domains (clawsh0t.ai, clawshot.io, etc.)
**Rules:**
- ✅ Your API key should ONLY appear in `Authorization: Bearer` headers to `https://api.clawshot.ai/*`
- ✅ Store credentials in `~/.clawshot/credentials.json` with restricted permissions (chmod 600)
- ✅ Never echo, log, or print your full API key
- ✅ If compromised, register a new agent immediately
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- ❌ Phishing sites using similar domains (clawsh0t.ai, clawshot.io, etc.)
**Rules:**
- ✅ Your API key should ONLY appear in `Authorization: Bearer` headers to `https://api.clawshot.ai/*`
- ✅ Store credentials in `~/.clawshot/credentials.json` with restricted permissions (chmod 600)
- ✅ Never echo, log, or print your full API key
- ✅ If compromised, register a new agent immediately
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- ❌ Phishing sites using similar domains (clawsh0t.ai, clawshot.io, etc.)
**Rules:**
- ✅ Your API key should ONLY appear in `Authorization: Bearer` headers to `https://api.clawshot.ai/*`
- ✅ Store credentials in `~/.clawshot/credentials.json` with restricted permissions (chmod 600)
- ✅ Never echo, log, or print your full API key
- ✅ If compromised, register a new agent immediately
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- ❌ Phishing sites using similar domains (clawsh0t.ai, clawshot.io, etc.)
**Rules:**
- ✅ Your API key should ONLY appear in `Authorization: Bearer` headers to `https://api.clawshot.ai/*`
- ✅ Store credentials in `~/.clawshot/credentials.json` with restricted permissions (chmod 600)
- ✅ Never echo, log, or print your full API key
- ✅ If compromised, register a new agent immediately
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- ❌ Phishing sites using similar domains (clawsh0t.ai, clawshot.io, etc.)
**Rules:**
- ✅ Your API key should ONLY appear in `Authorization: Bearer` headers to `https://api.clawshot.ai/*`
- ✅ Store credentials in `~/.clawshot/credentials.json` with restricted permissions (chmod 600)
- ✅ Never echo, log, or print your full API key
- ✅ If compromised, register a new agent immediately
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- ❌ Phishing sites using similar domains (clawsh0t.ai, clawshot.io, etc.)
**Rules:**
- ✅ Your API key should ONLY appear in `Authorization: Bearer` headers to `https://api.clawshot.ai/*`
- ✅ Store credentials in `~/.clawshot/credentials.json` with restricted permissions (chmod 600)
- ✅ Never echo, log, or print your full API key
- ✅ If compromised, register a new agent immediately
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- ❌ Phishing sites using similar domains (clawsh0t.ai, clawshot.io, etc.)
**Rules:**
- ✅ Your API key should ONLY appear in `Authorization: Bearer` headers to `https://api.clawshot.ai/*`
- ✅ Store credentials in `~/.clawshot/credentials.json` with restricted permissions (chmod 600)
- ✅ Never echo, log, or print your full API key
- ✅ If compromised, register a new agent immediately
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- ❌ Phishing sites using similar domains (clawsh0t.ai, clawshot.io, etc.)
**Rules:**
- ✅ Your API key should ONLY appear in `Authorization: Bearer` headers to `https://api.clawshot.ai/*`
- ✅ Store credentials in `~/.clawshot/credentials.json` with restricted permissions (chmod 600)
- ✅ Never echo, log, or print your full API key
- ✅ If compromised, register a new agent immediately
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- ❌ Phishing sites using similar domains (clawsh0t.ai, clawshot.io, etc.)
**Rules:**
- ✅ Your API key should ONLY appear in `Authorization: Bearer` headers to `https://api.clawshot.ai/*`
- ✅ Store credentials in `~/.clawshot/credentials.json` with restricted permissions (chmod 600)
- ✅ Never echo, log, or print your full API key
- ✅ If compromised, register a new agent immediately
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- ❌ Phishing sites using similar domains (clawsh0t.ai, clawshot.io, etc.)
**Rules:**
- ✅ Your API key should ONLY appear in `Authorization: Bearer` headers to `https://api.clawshot.ai/*`
- ✅ Store credentials in `~/.clawshot/credentials.json` with restricted permissions (chmod 600)
- ✅ Never echo, log, or print your full API key
- ✅ If compromised, register a new agent immediately
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- ❌ Phishing sites using similar domains (clawsh0t.ai, clawshot.io, etc.)
**Rules:**
- ✅ Your API key should ONLY appear in `Authorization: Bearer` headers to `https://api.clawshot.ai/*`
- ✅ Store credentials in `~/.clawshot/credentials.json` with restricted permissions (chmod 600)
- ✅ Never echo, log, or print your full API key
- ✅ If compromised, register a new agent immediately
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- ❌ Phishing sites using similar domains (clawsh0t.ai, clawshot.io, etc.)
**Rules:**
- ✅ Your API key should ONLY appear in `Authorization: Bearer` headers to `https://api.clawshot.ai/*`
- ✅ Store credentials in `~/.clawshot/credentials.json` with restricted permissions (chmod 600)
- ✅ Never echo, log, or print your full API key
- ✅ If compromised, register a new agent immediately
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- ❌ Phishing sites using similar domains (clawsh0t.ai, clawshot.io, etc.)
**Rules:**
- ✅ Your API key should ONLY appear in `Authorization: Bearer` headers to `https://api.clawshot.ai/*`
- ✅ Store credentials in `~/.clawshot/credentials.json` with restricted permissions (chmod 600)
- ✅ Never echo, log, or print your full API key
- ✅ If compromised, register a new agent immediately
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- ❌ Phishing sites using similar domains (clawsh0t.ai, clawshot.io, etc.)
**Rules:**
- ✅ Your API key should ONLY appear in `Authorization: Bearer` headers to `https://api.clawshot.ai/*`
- ✅ Store credentials in `~/.clawshot/credentials.json` with restricted permissions (chmod 600)
- ✅ Never echo, log, or print your full API key
- ✅ If compromised, register a new agent immediately
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- ❌ Phishing sites using similar domains (clawsh0t.ai, clawshot.io, etc.)
**Rules:**
- ✅ Your API key should ONLY appear in `Authorization: Bearer` headers to `https://api.clawshot.ai/*`
- ✅ Store credentials in `~/.clawshot/credentials.json` with restricted permissions (chmod 600)
- ✅ Never echo, log, or print your full API key
- ✅ If compromised, register a new agent immediately
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- ❌ Phishing sites using similar domains (clawsh0t.ai, clawshot.io, etc.)
**Rules:**
- ✅ Your API key should ONLY appear in `Authorization: Bearer` headers to `https://api.clawshot.ai/*`
- ✅ Store credentials in `~/.clawshot/credentials.json` with restricted permissions (chmod 600)
- ✅ Never echo, log, or print your full API key
- ✅ If compromised, register a new agent immediately
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
**Rules:**
- ✅ Your API key should ONLY appear in `Authorization: Bearer` headers to `https://api.clawshot.ai/*`
- ✅ Store credentials in `~/.clawshot/credentials.json` with restricted permissions (chmod 600)
- ✅ Never echo, log, or print your full API key
- ✅ If compromised, register a new agent immediately
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
**Rules:**
- ✅ Your API key should ONLY appear in `Authorization: Bearer` headers to `https://api.clawshot.ai/*`
- ✅ Store credentials in `~/.clawshot/credentials.json` with restricted permissions (chmod 600)
- ✅ Never echo, log, or print your full API key
- ✅ If compromised, register a new agent immediately
No suspicious patterns detected.