cosmos-vulnerability-scanner

Solid

Scans Cosmos SDK blockchain modules and CosmWasm contracts for consensus-critical vulnerabilities — chain halts, fund loss, state divergence. 25 core + 16 IBC + 10 EVM + 3 CosmWasm patterns. Use when auditing custom x/ modules, reviewing IBC integrations, or assessing pre-launch chain security. Updated for SDK v0.53.x.

AI & Automation 8,273 stars 715 forks Updated 6 days ago CC-BY-SA-4.0

Install

View on GitHub

Quality Score: 90/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Cosmos Vulnerability Scanner ## Purpose Scan Cosmos SDK modules and CosmWasm contracts for vulnerabilities that cause chain halts, consensus failures, or fund loss. Spawns parallel scanning agents — each specializing in a vulnerability category — that return findings to the main skill, which then writes them as individual markdown files to an output directory. **Output directory**: defaults to `.bughunt_cosmos/`. If the user specifies a different directory in their prompt, use that instead. ## When to Use - Auditing Cosmos SDK modules (custom `x/` modules) - Reviewing CosmWasm smart contracts - Pre-launch security assessment of Cosmos chains - Investigating chain halt incidents ## When NOT to Use - Pure Solidity/EVM audits without Cosmos SDK — use Solidity-specific tools - CometBFT consensus engine internals — this covers SDK modules, not the consensus layer itself - General Go code review with no blockchain context - Cosmos SDK application logic that is not consensus-critical (e.g., CLI commands, REST endpoints) - CosmWasm contract-only audits on chains without custom SDK modules — use the CosmWasm checklist items alone ## Essential Principles 1. **Consensus path is king** — A bug only matters for chain halt/fund loss if it's on the consensus-critical execution path (BeginBlock, EndBlock, FinalizeBlock, msg_server handlers, AnteHandler). Always verify a finding is reachable from consensus before reporting it. 2. **State divergence = chain halt** — Any non-determin...

Details

Author
trailofbits
Repository
trailofbits/skills
Created
10 months ago
Last Updated
6 days ago
Language
Python
License
CC-BY-SA-4.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

cosmos-vulnerability-scanner

Scans Cosmos SDK blockchain modules and CosmWasm contracts for consensus-critical vulnerabilities — chain halts, fund loss, state divergence. 25 core + 16 IBC + 10 EVM + 3 CosmWasm patterns. Use when auditing custom x/ modules, reviewing IBC integrations, or assessing pre-launch chain security. Updated for SDK v0.53.x.

1 Updated 2 months ago
gztes
AI & Automation Listed

vuln-scan

Use this skill when the user runs /ievo:vuln-scan, asks to scan for vulnerabilities, or says "security scan my code" — not for auditing a third-party skill/plugin before installation (use /ievo:security-check for that). CWE-aware deep source code vulnerability scan for a single module or file set, inspired by Project Glasswing. Uses AI reasoning (not regex) to trace data flows, detect vulnerabilities, and validate findings via complete exploit chains. Every finding requires an attack narrative (entry point, data flow, impact); no chain means no finding. Applied per-module by the vuln-scanner agent, orchestrated by the /ievo:vuln-scan command. Covers OWASP top 10, CWE-anchored threat taxonomy (injection, auth bypass, crypto misuse, data exposure, race conditions, deserialization, path traversal, SSRF, business logic, supply chain).

1 Updated 2 months ago
ievo-ai
Data & Documents Listed

scv-scan

Systematically audit Solidity smart contract codebases for security vulnerabilities using a 4-phase approach - load a vulnerability cheatsheet, sweep code with grep and semantic analysis, deep-validate candidates against reference files, and output a severity-ranked findings

110 Updated 8 months ago
kadenzipfel