Back to skill

Security audit

Siebly Crypto Exchange API

Security checks for vulnerabilities and agentic risk

Overview

ClawScan rates this skill benign with medium confidence: the reported findings were judged expected for its stated crypto exchange API purpose, though one local reference was missing and the scan is partial.

The verdict is benign, not a guarantee of safety. Skillspector reports partial analysis because a local path-like reference could not be resolved, although it scanned the one listed component; consider that gap and the instruction-scope note when deciding whether to install.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (4)

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · SKILL.md (reported line 54)May include surrounding context.

md
5. Use the [examples hub](https://siebly.io/examples) as an implementation reference.
6. Start with public market data or read-only account access before trading workflows. Mock trading workflows when useful to validate integration boundaries.
7. Add validation for missing credentials during startup.
8. If the Node.js project uses environment variables or creates .env.example, make .env loading automatic for every normal local entrypoint before config parsing. Prefer Node.js built-in --env-file/--env-file-if-exists in package scripts when supported by the project runtime; otherwise use process.loadEnvFile, dotenv/config, or the repo-local env loader. Document that real process environment variables override .env. Ensure all variables in the .env.example are commented clearly with their purpose and accepted values, and that the README references the .env.example and documents .env loading and precedence.
9. For TypeScript projects, use Node16, NodeNext, or the repo-compatible module/mod

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · SKILL.md (reported line 54)May include surrounding context.

md
es .env.example, make .env loading automatic for every normal local entrypoint before config parsing. Prefer Node.js built-in --env-file/--env-file-if-exists in package scripts when supported by the project runtime; otherwise use process.loadEnvFile, dotenv/config, or the repo-local env loader. Document that real process environment variables override .env. Ensure all variables in the .env.example are commented clearly with their purpose and accepted values, and that the README references the .env.example and documents .env loading and precedence.
9. For TypeScript projects, use Node16, NodeNext, or the repo-compatible module/moduleResolution settings. Under strict optional property settings, omit undefined optional REST request fields rather than sending them as undefined.
10. Add logging and clear error handling for rate limits, authentication failures, reconnect behavior, and rejected requests.
11. For WebSockets, handle reconnects, subscriptions, message events, and clean shutdown.

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
80% confidence
Finding

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.

Content

Scanner excerpt · SKILL.md (reported line 140)May include surrounding context.

md
## Safety Rules

- Never ask the user to paste API keys, secrets, passphrases, private keys, or seed phrases into chat.
- Never write secrets into source files, examples, tests, or logs.
- No exchange write path can run before [EXECUTION_MODE](https://siebly.io/reference/glossary, TESTNET, or LIVE is explicitly selected and every configured gate allows it.
- Prefer read-only keys for account queries.

Skill Enumeration

Medium
Category
Agent Snooping
Confidence
80% confidence
Finding

Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.

Content

Scanner excerpt · SKILL.md (reported line 179)May include surrounding context.