unsecure-signatures

Name: unsecure-signatures
Availability: InStock
Author: Apeguru

Detect unsecure ECDSA signature implementations in Solidity smart contracts.

1|1|Updated Feb 18, 2026

Search Tags:#security #vulnerability #audit #smart contracts #solidity #signatures #ecdsa

Ready to run

npx skills add https://github.com/Apegurus/solidity-argus --skill unsecure-signatures

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: unsecure-signatures
Source: https://github.com/Apegurus/solidity-argus/tree/main/skills/vulnerability-patterns/unsecure-signatures
Command: npx skills add https://github.com/Apegurus/solidity-argus --skill unsecure-signatures

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies and helps remediate critical vulnerabilities in smart contracts that rely on ECDSA signatures for authorization or verification, preventing exploits like replay attacks and unauthorized access.

Core Features & Use Cases

Signature Vulnerability Detection: Analyzes contracts for common pitfalls in ECDSA signature handling.
Replay Protection Check: Verifies the inclusion of nonces, chainIds, and contract addresses in signed messages.
Malleability & Null Address Checks: Detects issues with signature malleability and unchecked ecrecover return values.
Use Case: A developer can use this Skill to audit a new DeFi protocol's signature verification logic, ensuring that users cannot be exploited through replay attacks or by forging signatures.

Quick Start

Audit the attached contract file 'VaultContract.sol' for unsecure signature vulnerabilities.

Frequently Asked Questions about unsecure-signatures

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

FAQPage Schema

How do I detect signature malleability vulnerabilities in Solidity smart contracts?▼

You can audit Solidity smart contracts for replay attack vulnerabilities by checking for missing replay protection mechanisms like nonces, chainIds, and contract addresses in signed messages, which this Skill analyzes to ensure secure ECDSA signature verification.

Why does using abi.encodePacked cause hash collisions in signature verification?▼

Using abi.encodePacked causes hash collisions in signature verification because it allows dynamic parameters to be manipulated, and this Skill detects such hash collisions from abi.encodePacked usage to secure your smart contract authorization logic.

How do I implement EIP-712 structured data signing to secure smart contract signatures?▼

To implement EIP-712 structured data signing and secure smart contract signatures, this Skill identifies the lack of EIP-712 structured data signing in your code and provides remediation guidance with secure code examples for robust ECDSA verification.

Can this Skill audit an attached Solidity contract file for unsecure ECDSA signatures?▼

Yes, this Skill can audit an attached Solidity contract file for unsecure ECDSA signatures by analyzing the file directly, detecting vulnerabilities like signature malleability and missing replay protection, and outputting actionable remediation steps.

What are the limitations when auditing smart contracts for unsecure signature implementations?▼

A limitation when auditing smart contracts for unsecure signature implementations is that the Skill focuses specifically on ECDSA vulnerabilities like malleability and replay protection, requiring a provided contract file to execute its vulnerability analysis.