cosmos-vulnerability-scanner

Scans Cosmos SDK modules and CosmWasm contracts for consensus-critical vulnerabilities.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Ayoub-ouederni/SENTINEL --skill cosmos-vulnerability-scanner-ayoub-ouederni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cosmos-vulnerability-scanner
Source: https://github.com/Ayoub-ouederni/SENTINEL/tree/main/.claude/skills/cosmos-vulnerability-scanner
Command: npx skills add https://github.com/Ayoub-ouederni/SENTINEL --skill cosmos-vulnerability-scanner-ayoub-ouederni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Auditing Cosmos SDK chains for consensus-critical bugs requires deep knowledge of dozens of vulnerability classes across SDK modules, IBC, EVM precompiles, and CosmWasm contracts, and missing one pattern can mean a chain halt or fund loss. ## Core Features & Use Cases - Parallel multi-agent scanning: Spawns specialized scanning agents covering 25 core, 16 IBC, 10 EVM, and 3 CosmWasm vulnerability patterns, each grounded in real advisories like Dragonberry, ASA-2024-007, and the Saga $7M exploit. - Automated discovery and threat modeling: Generates a CLAUDE.md technical inventory capturing SDK version, custom modules, ABCI hooks, AnteHandler chain, and trust boundaries before scanning. - Structured findings output: Writes each verified finding as an individual markdown file with severity, location, vulnerable code, attack scenario, and recommendation. - Use Case: Before launching a custom Cosmos chain with IBC and EVM support, run the scanner against the repo to catch signer annotation mismatches, IBC reentrancy, and EVM/Cosmos state desync bugs. ## Quick Start Scan the Cosmos SDK codebase in this repository for consensus-critical vulnerabilities and write the findings to the default output directory.

Frequently Asked Questions about cosmos-vulnerability-scanner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a Cosmos SDK module for vulnerabilities?

Run the scanner against the target repository path. It first generates a discovery document with SDK version, modules, and threat model, then spawns parallel agents that check each vulnerability pattern and write findings as markdown files.

What vulnerability classes does a Cosmos security scanner cover?

It covers 25 core SDK patterns (non-determinism, ABCI panics, signer mismatches), 16 IBC patterns (reentrancy, denom confusion, PFM escrow bugs), 10 EVM patterns (precompile state desync), and 3 CosmWasm patterns.

Does the scanner support Cosmos SDK v0.53?

Yes, all patterns were re-validated against cosmos-sdk v0.53.x, including ABCI 2.0 interfaces, proto signer annotations replacing GetSigners, and the deprecation of ValidateBasic. It checks go.mod versions before applying patterns.

Can it scan CosmWasm contracts and IBC integrations?

Yes, conditional agents scan CosmWasm contracts for wrapping overflow and non-deterministic queries, and IBC code for reentrancy, timeout handling, and ICA misconfiguration when those platforms are detected during discovery.

When should I not use this Cosmos vulnerability scanner?

Avoid it for pure Solidity/EVM audits without Cosmos SDK, CometBFT consensus engine internals, general Go review without blockchain context, and non-consensus code like CLI commands or REST endpoints.