KyberSwap Arbitrage

WarnAudited by ClawScan on May 10, 2026.

Overview

The skill is coherent for crypto arbitrage, but it tells an agent to execute irreversible on-chain trades without clear wallet credential declarations, spending limits, or required user confirmation.

Only use this with a dedicated low-balance wallet and manual transaction review. Set strict limits for token addresses, trade size, gas, slippage, recipient, and deadline, and simulate quotes before allowing any real transaction.

Findings (2)

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.

High

#ASI02: Tool Misuse and Exploitation

What this means

If used with a wallet-capable agent, it could spend user funds, incur gas costs, or make losing trades without sufficiently explicit guardrails.

Why it was flagged

This instructs the agent to execute an on-chain DEX trade. The artifacts do not require a separate user confirmation step, maximum spend, approved token list, or dry-run before submitting a financial transaction.

Skill content

const tx = await router.swapExactTokensForTokens(
  amountIn,
  amountOutMin,
  path,
  recipient,
  deadline
);

Recommendation

Require manual user confirmation for every transaction and define hard limits for tokens, amount, slippage, gas, deadline, and recipient before execution.

High

#ASI03: Identity and Privilege Abuse

What this means

Users may not realize the skill needs access to a funded wallet or approval to spend tokens, which is a significant privilege boundary.

Why it was flagged

Executing Base network trades requires wallet signing and token-spending authority, but the registry metadata declares no primary credential, required environment variables, or configuration paths.

Skill content

description: Execute triangular arbitrage on Base network via KyberSwap. Use for: ... Executing multi-hop trades

Recommendation

Declare wallet/signing requirements clearly, recommend a dedicated limited-balance wallet, and avoid using private keys or broad token approvals unless the user explicitly opts in.