blockchain-security — Claude Code skill
Tests Solidity contracts and blockchain CTF challenges for common EVM flaws. Use it when reviewing storage, delegatecall paths, or access checks.
npx skills add transilienceai/communitytools --skill blockchain-security -a claude-codeWhat blockchain-security does
The skill takes a contract review from source or bytecode through storage mapping and privileged operations. It covers reentrancy, access control, tx.origin, integer overflow, weak randomness, empty-array validation bypasses, and ECDSA signature malleability.
For delegatecall cases, it calls for matching the exploit contract's storage slot order to the target. An exact storage layout match is mandatory here, or writes land in the wrong slots. It also covers CREATE address prediction, reading private values with eth_getStorageAt, and checking an isSolved() condition.
Its examples use web3.py, cast, or forge; compilation uses solcx with Solidity 0.8.13. The skill suggests scripting a full CTF flow because challenge instances can be temporary.
What it helps with
- check a Solidity contract for reentrancy
- find missing access checks
- predict a
CREATEcontract address - read a storage slot with
eth_getStorageAt - inspect an empty-array validation bypass
Example prompts for the agent
- Review this Solidity contract for
delegatecall, reentrancy, and access-control issues. - Map the storage layout and inspect private values with
eth_getStorageAt. - Help solve this blockchain CTF and verify
isSolved().
How to install blockchain-security
1Skills CLI (Vercel)
npx skills add transilienceai/communitytools --skill blockchain-security -a claude-code2Manually: put the files in place
~/.claude/skills/blockchain-security/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/blockchain-security/
1Skills CLI (Vercel)
npx skills add transilienceai/communitytools --skill blockchain-security -a codex2Manually: put the files in place
.agents/skills/blockchain-security/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add transilienceai/communitytools --skill blockchain-security -a cursor2Manually: put the files in place
.cursor/skills/blockchain-security/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install transilienceai/communitytools blockchain-security2Manually: put the files in place
.github/skills/blockchain-security/SKILL.md1Skills CLI (Vercel)
npx skills add transilienceai/communitytools --skill blockchain-security -a gemini-cli2Platform CLI
gemini skills install https://github.com/transilienceai/communitytools --path skills/blockchain-securityManually: put the files in place
.devin/skills/blockchain-security/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add transilienceai/communitytools --skill blockchain-security -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about blockchain-security
How do I install blockchain-security in Claude Code?
Run npx skills add transilienceai/communitytools --skill blockchain-security -a claude-code, then run npx skills add transilienceai/communitytools --skill blockchain-security -a claude-code again. The skill file is placed at ~/.claude/skills/blockchain-security/SKILL.md.
What does blockchain-security do?
It guides Solidity contract reviews and blockchain CTF work. The skill covers EVM vulnerability checks, storage slots, delegatecall, and CREATE address prediction.
What is required for a delegatecall attack path?
The exploit contract must mirror the target contract's storage layout, including slot order. This matters because the called code uses the caller's storage.
Source text
SKILL.md · MIT
---
name: blockchain-security
description: Smart contract security testing and blockchain CTF exploitation. Covers Solidity vulnerability analysis, EVM storage manipulation, delegatecall attacks, CREATE/CREATE2 address prediction, and common DeFi exploit patterns. Use when analyzing Solidity contracts, solving blockchain challenges, or testing smart contract security.
---
# Blockchain Security
## Quick Start
1. Download and decompile contracts (source or bytecode)
2. Map storage layout and identify privileged operations
3. Check for delegatecall, CREATE address prediction, reentrancy, access control
4. Deploy exploit contracts via web3.py or cast/forge
5. Verify win condition (isSolved/flag endpoint)
## Blockchain CTF Challenge Pattern
```bash
# Get connection info
curl http://$HOST:$PORT/connection_info # -> PrivateKey, Address, TargetAddress, setupAddress
# RPC endpoint
RPC_URL="http://$HOST:$PORT/rpc"
# Win condition: Setup.isSolved() must return true
```
## Key Attack Vectors
### 1. Delegatecall Storage Manipulation
When contract A does `delegatecall` to contract B, B's code runs with A's storage.
- Deploy exploit contract that mirrors A's storage layout
- Exploit contract writes to A's storage slots via delegatecall
- **Critical**: Storage layout must match exactly (same slot ordering)
- See [reference/delegatecall-attacks.md](reference/delegatecall-attacks.md)
### 2. CREATE Address Prediction (Nonce Manipulation)
Contract addresses from CREATE are deterministic: `keccak256(rlp([sender, nonce]))[12:]`
- Brute-force nonce to find which nonce produces target address
- Send dummy transactions (self-transfers) to increment nonce
- Deploy exploit contract at the exact nonce that hits target address
- See [reference/create-address-prediction.md](reference/create-address-prediction.md)
### 3. Storage Layout & Slot Computation
- Mappings: `keccak256(h(key) || uint256(slot_number))`
- Value types: `h(k) = abi.encode(k)` (left-padded to 32 bytes)
- String/bytes: `h(k) = keccak256(k)`
- Read private variables via `eth_getStorageAt`
- See [reference/storage-layout.md](reference/storage-layout.md)
### 4. Empty Array / Zero-Length Input Bypass
When a function loops over a user-supplied array to validate items (signatures, approvals, votes), passing an **empty array** skips the loop entirely. If there's no minimum-length check, validation is bypassed.
- Check: `for (uint i = 0; i < arr.length; i++)` with no `require(arr.length >= N)`
- Exploit: Call the function with `[]` to skip all validation
### 5. ECDSA Signature Malleability
Raw `ecrecover` accepts both `(v, r, s)` and `(v', r, N-s)` (where N = secp256k1 order, v flipped 27↔28). If a contract deduplicates signatures by hash of raw bytes, the malleable form has a different hash but recovers to the same signer.
- Check: `ecrecover` used without `s <= N/2` enforcement (OpenZeppelin's ECDSA.sol enforces this)
- Exploit: Take a known valid signature, compute `new_s = N - s`, flip `v`, submit as "new" signature
### 6. Common Vulnerability Classes
| Vulnerability | Check |
|---|---|
| Reentrancy | External calls before state updates |
| Access control | Missing onlyOwner / msg.sender checks |
| Integer overflow | Solidity < 0.8.0 without SafeMath |
| Delegatecall injection | User-controlled delegatecall target |
| tx.origin auth | `tx.origin` instead of `msg.sender` |
| Selfdestruct | Force-send ETH, reset contract nonce |
| Weak randomness | blockhash/timestamp as entropy source |
| Empty array bypass | Loop validation with no min-length check |
| Signature malleability | Raw ecrecover without s-normalization |
## Tools
```python
# web3.py essentials
from web3 import Web3
w3 = Web3(Web3.HTTPProvider(RPC_URL))
acct = w3.eth.account.from_key(PRIVATE_KEY)
# Read private storage
w3.eth.get_storage_at(contract_addr, slot)
# Deploy contract
from solcx import compile_source, install_solc
install_solc("0.8.13")
compiled = compile_source(source, output_values=["abi", "bin"], solc_version="0.8.13")
# Send raw bytecode deployment
tx = {'data': bytecode, 'gas': 3000000, 'gasPrice': w3.eth.gas_price, 'nonce': nonce, 'chainId': chain_id}
signed = acct.sign_transaction(tx)
w3.eth.send_raw_transaction(signed.raw_transaction)
```
## Reference
- [Delegatecall Attacks](reference/delegatecall-attacks.md)
- [CREATE Address Prediction](reference/create-address-prediction.md)
- [Storage Layout](reference/storage-layout.md)
## Critical Rules
- Always read storage before attacking (private vars are readable on-chain)
- Mirror exact storage layout when exploiting delegatecall
- For CREATE nonce brute-force, check nonces 0-100000+ systematically
- CTF instances are often ephemeral -- script the full attack for speed
© transilienceai · MIT · transilienceai/communitytools