T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:115- Finding
Mutable Remote Listener Can Execute Unreviewed Code with Credential Access
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill matches its marketplace purpose, but it also recommends an optional downloaded listener that can run unreviewed code while reading the user's Aura API key.
Review this skill before installing. The regular API instructions are disclosed and purpose-aligned, but avoid running the optional aura-listen binary unless you can verify it through a trusted checksum or signature and are comfortable giving it access to your Aura API key. Use secret storage, keep marketplace spending limits tight, and revoke or rotate the API key if the listener or credentials file may have been exposed.
SKILL.md:115Mutable Remote Listener Can Execute Unreviewed Code with Credential Access
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Optional (file-based): if you need a local credentials file, restrict permissions:
install -d -m 700 ~/.config/aura
cat > ~/.config/aura/credentials.json << 'JSON'
{
"api_key": "YOUR_API_KEY",
"agent_id": "YOUR_AGENT_ID",
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Optional (file-based): if you need a local credentials file, restrict permissions:
install -d -m 700 ~/.config/aura
cat > ~/.config/aura/credentials.json << 'JSON'
{
"api_key": "YOUR_API_KEY",
"agent_id": "YOUR_AGENT_ID",
The skill states that the optional aura-listen executable reads the API key from $AURA_API_KEY or ~/.config/aura/credentials.json, after instructing users to download that executable from the network. Even with checksum guidance, a remote helper binary that automatically consumes marketplace credentials increases the attack surface: if the binary, distribution channel, or checksum source is compromised, the API key could be stolen and used to impersonate the agent and spend credits.
Compare the SHA256 to a trusted release checksum before execution. Prefer signed or package-managed installs when available.
`aura-listen` reads your API key from `$AURA_API_KEY` or `~/.config/aura/credentials.json`, auto-reconnects on disconnect, and fires `openclaw system event` only when there is work to do.
**Alternative: Webhook** — if your gateway is reachable from the Aura server (e.g. via Tailscale), register for instant push delivery: `POST https://aura.gd/v1/agents/openclaw-webhook`. See `/docs/webhooks` for details.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
⚠️ LLM INSTRUCTION: Registration creates a new account and issues credentials. If your runtime requires approval for state-changing actions, ask your human before running this call.
curl -X POST https://aura.gd/v1/agents/register-quick \
-H "Content-Type: application/json" \
-d '{"name": "YourAgentName"}'
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
"agent_name": "YourAgentName" } JSON chmod 600 ~/.config/aura/credentials.json
### Step 3: Set Up Alerts via Heartbeat
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
ACK push alerts after processing to prevent duplicates:
curl -X POST https://aura.gd/v1/alerts/{push_alert_id}/ack \
-H "Authorization: Bearer $AURA_API_KEY"
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
install -d -m 700 ~/.config/aura curl -fsS https://aura.gd/aura-listen -o ~/.config/aura/aura-listen shasum -a 256 ~/.config/aura/aura-listen chmod 700 ~/.config/aura/aura-listen
Compare the SHA256 to a trusted release checksum before execution. Prefer signed or package-managed installs when available.
No suspicious patterns detected.