Bitstamp Trader

AdvisoryAudited by Static analysis on Apr 30, 2026.

Overview

No suspicious patterns detected.

Findings (0)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

ConcernMedium Confidence

ASI02: Tool Misuse and Exploitation

What this means

A real Bitstamp order could be placed for smaller amounts if --live is used, even though the skill documentation says live trades should always get explicit confirmation.

Why it was flagged

The visible in-tool confirmation gate applies only to live trades at or above the configurable large-trade threshold. Lower-value live trades can continue after the --live flag without this script-level prompt, so accidental or autonomous invocation could still create real financial exposure.

Skill content

if live and est_usd >= cfg["large_trade_threshold_usd"]:
        ...
        confirm = input("   Type CONFIRM to proceed: ")

Recommendation

Only allow live trading after a clear human confirmation, keep default limits low, and consider requiring an in-tool confirmation prompt for every live order regardless of size.

NoteHigh Confidence

ASI03: Identity and Privilege Abuse

What this means

If the API key has excessive permissions or is exposed, someone could trade on the account, and possibly do more if withdrawals were enabled.

Why it was flagged

The skill requires Bitstamp API credentials for account and trading operations. The permission guidance is appropriate for the purpose, but these credentials still grant financial account access and should be tightly scoped.

Skill content

export BITSTAMP_API_KEY="your-key"
export BITSTAMP_API_SECRET="your-secret"

... create an API key with **Orders** permission only (NO Withdrawals). Enable **IP whitelisting**.

Recommendation

Use a dedicated Bitstamp API key with orders/trading only, no withdrawals, IP whitelisting, and low exchange-side limits where possible.

NoteHigh Confidence

ASI04: Agentic Supply Chain Vulnerabilities

What this means

A bad or unexpected dependency version could affect a tool that has access to a trading account.

Why it was flagged

The script depends on ccxt and gives a manual unpinned pip install instruction, while the provided install spec declares no dependencies. This is expected for a CCXT-based trading CLI but leaves package version selection to the user.

Skill content

print("ERROR: ccxt not installed. Run:")
print(f"  source {SKILL_DIR}/.venv/bin/activate && pip install ccxt")

Recommendation

Install dependencies from trusted sources, pin a known-good ccxt version, and review the environment before enabling live trading.

NoteHigh Confidence

ASI06: Memory and Context Poisoning

What this means

Local files may disclose trading history to anyone with access to the account, and changes to local config or kill-switch files can influence future trades.

Why it was flagged

The skill intentionally persists audit logs and control state that can reveal trading activity and affect future trading behavior.

Skill content

Audit Trail — Every action logged to `~/.config/bitstamp-trader/audit.jsonl`
...
The kill switch creates a lock file at `~/.config/bitstamp-trader/KILL_SWITCH`.

Recommendation

Keep the config directory private, avoid sharing audit logs, and review config or kill-switch state before live trading.