Empire Builder
Security checks across static analysis, malware telemetry, and agentic risk
Overview
Empire Builder is a coherent crypto treasury integration, but it needs careful review because it enables live mainnet treasury/admin actions and leaves some credential/signature safeguards to the operator.
Install only if you intentionally want an agent to help operate Empire Builder on live Base/Arbitrum mainnet. Do not provide private keys to the agent, keep API keys out of URLs when possible, require manual wallet confirmation for every transaction, and verify all recipients, amounts, chains, vault addresses, and signed-message text before approving.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
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.
An agent-assisted transaction could spend gas or move treasury funds on Base/Arbitrum mainnet if the user signs it without checking the decoded calls.
The skill tells agents how to use API-prepared calldata for owner-signed mainnet treasury payouts. This is central to the product, but mistakes or unreviewed signing can move funds irreversibly.
submit executeBatch on contractAddress using supplied calls or raw data — caller pays gas. Confirm chainId, vault contractAddress, and calldata match the prepare response before broadcasting.
Require explicit human approval before every wallet signature; decode calldata; verify chain ID, vault address, recipients, amounts, and transaction hash status before storing distributions.
A leaked API key, vague signed message, or reused signature could make unintended leaderboard/admin mutations easier if other controls do not stop it.
Write APIs depend on API keys and guardian signatures, but the docs allow API keys in query parameters and state that some signature scope/replay protections are not enforced server-side.
x-api-key header (or api_key query) ... Message format: for leaderboard creates the backend does not enforce a specific template ... Include timestamp + nonce to reduce replay risk ... server currently does not enforce these
Prefer the x-api-key header over query strings, use least-privilege/rotatable keys, and only sign unique human-readable messages with explicit action, empire ID, timestamp, and nonce.
If you perform token deployment workflows, you will rely on external packages and the integrity of the copied skill documentation.
The deploy workflow may require external npm packages and a remote skill copy. The versions are pinned and verification is recommended, so this is a supply-chain note rather than a hidden install concern.
dependencies: [clanker-sdk@4.2.16, viem@2.48.0] ... npm install clanker-sdk@4.2.16 viem@2.48.0 ... use a lockfile ... diff against a trusted checkout
Install only pinned versions, use a lockfile, verify the skill source against a trusted copy, and avoid @latest in automation.