cosmos-vulnerability-scanner

Detect consensus-critical vulnerabilities in Cosmos SDK modules and CosmWasm contracts.

Updated May 2, 2026
One-click install
npx skills add https://github.com/ayehiaa/my-travel-assistant --skill cosmos-vulnerability-scanner-ayehiaa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cosmos-vulnerability-scanner
Source: https://github.com/ayehiaa/my-travel-assistant/tree/main/.agents/skills/cosmos-vulnerability-scanner
Command: npx skills add https://github.com/ayehiaa/my-travel-assistant --skill cosmos-vulnerability-scanner-ayehiaa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Cosmos SDK and IBC integrations can fail in ways that stop the chain or risk fund loss, and these issues are hard to catch with generic code reviews alone.

Core Features & Use Cases

  • Consensus-path vulnerability scanning: Guides a multi-agent audit across non-determinism, ABCI lifecycle hazards, signer/validation mismatches, and ante-handler security.
  • IBC-focused pattern coverage: Detects IBC integration risks like callback/CEI violations, denom handling issues, packet timeout mistakes, and event/middleware determinism problems.
  • Cross-runtime scope (EVM + CosmWasm): Extends checks to Cosmos EVM desync classes and CosmWasm-specific patterns that can amplify IBC or consensus risks.
  • Actionable finding outputs: Writes each detected issue to a dedicated markdown file in an output directory for follow-up remediation.

Quick Start

Run the cosmos-vulnerability-scanner against your chain repository at the root path you provide, and generate a folder of markdown findings you can review with your engineering team.

Frequently Asked Questions about cosmos-vulnerability-scanner

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

FAQPage Schema
How do I scan Cosmos SDK modules for consensus-critical vulnerabilities?

Scanning Cosmos SDK modules for consensus-critical vulnerabilities involves running a pattern-matching audit against your chain repository root. The scanner identifies non-determinism, ABCI hazards, and IBC integration risks, generating markdown findings for your team to review.

What types of IBC security risks should I audit before launching a Cosmos chain?

Before launching a Cosmos chain, audit IBC security risks including callback/CEI violations, denom handling issues, packet timeout mistakes, and middleware determinism problems. Scanning detects these integration risks early to prevent chain halts or fund loss.

Can I use a vulnerability scanner to audit CosmWasm contracts and EVM components together?

Yes, you can audit CosmWasm contracts and EVM components together. The scanner extends checks to Cosmos EVM desync classes and CosmWasm-specific patterns that can amplify IBC or consensus risks, providing cross-runtime security coverage for your chain.

How do I find non-determinism and ABCI lifecycle hazards in go.mod version-aware Cosmos codebases?

Finding non-determinism and ABCI lifecycle hazards in Cosmos codebases requires deterministic grep and glob searches with version-aware reasoning from go.mod. The scanner checks behavior changes across versions like v0.47, v0.50, and v0.53 to ensure consensus-path relevance.

Does this Cosmos code audit tool work with ibc-go keepers and x/ibc modules?

Yes, this Cosmos code audit tool works with ibc-go keepers and x/ibc modules. It applies scans to codebases containing IBC integrations, checking for packet timeout mistakes, callback violations, and event determinism problems across IBC integration paths.

What is the best way to triage consensus-critical Cosmos bugs during incident response?

The best way to triage consensus-critical Cosmos bugs during incident response is running agent-parallel execution with deterministic searches against the chain repository. This generates complete per-pattern markdown findings for immediate remediation and follow-up.