cosmos-vulnerability-scanner

Scan Cosmos SDK blockchains and CosmWasm contracts for consensus-critical vulnerabilities.

1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/allanninal/claude-code-skills --skill cosmos-vulnerability-scanner-allanninal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cosmos-vulnerability-scanner
Source: https://github.com/allanninal/claude-code-skills/tree/main/skills/cosmos-vulnerability-scanner
Command: npx skills add https://github.com/allanninal/claude-code-skills --skill cosmos-vulnerability-scanner-allanninal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies and helps fix critical security vulnerabilities in Cosmos SDK blockchains and CosmWasm smart contracts, preventing chain halts and fund loss.

Core Features & Use Cases

  • Vulnerability Detection: Scans for 9 specific consensus-critical patterns like non-determinism, incorrect signers, and ABCI panics.
  • Code Auditing: Assists in security reviews of custom Cosmos SDK modules and CosmWasm contracts.
  • Use Case: Before launching a new Cosmos chain, use this Skill to audit your custom modules for common consensus failures and security flaws.

Quick Start

Use the cosmos-vulnerability-scanner skill to audit the current project for security vulnerabilities.

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 Cosmos SDK modules for consensus-critical vulnerabilities before a chain launch?

To audit Cosmos SDK modules for consensus-critical vulnerabilities, scan the codebase for non-determinism, incorrect signer validation, and ABCI panics. This process identifies security flaws that could cause chain halts or fund loss during pre-launch assessments.

What consensus-critical vulnerabilities should I look for in CosmWasm smart contracts?

Consensus-critical vulnerabilities in CosmWasm smart contracts include non-determinism, incorrect signer validation, ABCI method panics, and bookkeeping errors. Scanning for these 9 specific patterns prevents chain halts and secures Cosmos SDK blockchains against fund loss.

Can I use this scanner to check for non-determinism and ABCI panics in custom Cosmos SDK modules?

Yes, you can scan custom Cosmos SDK modules for non-determinism and ABCI panics. The scanner identifies 9 consensus-critical vulnerabilities, assisting security reviews of custom modules to ensure blockchain stability and prevent consensus failures before deployment.

Why does my Cosmos blockchain halt, and how can a vulnerability audit fix it?

Cosmos blockchains halt due to consensus-critical vulnerabilities like non-determinism, incorrect signers, and ABCI panics. A vulnerability audit scans for these 9 specific patterns, identifying bookkeeping errors and security flaws so you can fix them before launch.

What's the best way to run a pre-launch security assessment for a Cosmos-based project?

The best way to run a pre-launch security assessment for a Cosmos-based project is to scan for 9 consensus-critical vulnerabilities, including non-determinism and incorrect signer validation. This identifies potential chain halts and fund loss risks in custom modules and CosmWasm contracts.

Does the Cosmos vulnerability scanner detect bookkeeping errors in CosmWasm contracts?

Yes, the Cosmos vulnerability scanner detects bookkeeping errors in CosmWasm contracts. It scans for 9 consensus-critical patterns, including non-determinism and ABCI panics, facilitating comprehensive security audits and pre-launch assessments for Cosmos-based projects.