access-control

Detect access control vulnerabilities in Solidity smart contracts.

60|18|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/PurpleAILAB/Vigilo --skill access-control-purpleailab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: access-control
Source: https://github.com/PurpleAILAB/Vigilo/tree/main/packages/claude/skills/vulnerability-patterns/access-control
Command: npx skills add https://github.com/PurpleAILAB/Vigilo --skill access-control-purpleailab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies and helps prevent critical access control vulnerabilities in smart contracts, which are a leading cause of fund loss in Web3.

Core Features & Use Cases

  • Vulnerability Detection: Pinpoints common access control flaws like missing modifiers, privilege escalation, and incorrect permission logic.
  • Root Cause Analysis: Explains why these bugs occur, aiding developers in writing more secure code.
  • Core Artifact: Guides the creation of a Permission Matrix to map contract functions, their sensitivity, and required roles.
  • Use Case: An auditor uses this Skill to quickly scan a new DeFi protocol's smart contracts, flagging functions that allow unauthorized state changes before deployment.

Quick Start

Analyze the provided Solidity code for access control vulnerabilities.

Frequently Asked Questions about access-control

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

FAQPage Schema
How do I detect access control vulnerabilities in Solidity smart contracts?

Detect access control vulnerabilities in Solidity smart contracts by analyzing code to identify missing modifiers, privilege escalation, tx.origin phishing, incorrect OR/AND logic, and missing two-step transfers. The analysis provides root cause explanations and specific detection patterns for each identified flaw.

What are common access control flaws in Web3 security?

Common access control flaws in Web3 security include missing modifiers, unauthorized privilege escalation, tx.origin phishing exploits, incorrect OR/AND permission logic, and missing two-step transfer patterns. These vulnerabilities frequently lead to unauthorized state changes and critical fund loss.

How do I create a permission matrix for smart contract auditing?

Create a permission matrix for smart contract auditing by mapping contract functions, their sensitivity levels, and required roles. This matrix serves as a core artifact to systematically verify that only authorized users can execute privileged operations and modify state.

Why does tx.origin phishing cause unauthorized access in smart contracts?

tx.origin phishing causes unauthorized access in smart contracts because using tx.origin for authentication allows attackers to trick users into triggering privileged functions through intermediate contracts. Root cause analysis reveals that msg.sender should be used instead to validate the immediate caller.

Can I scan a DeFi protocol for missing modifiers before deployment?

Scan a DeFi protocol for missing modifiers before deployment by running a comprehensive access control analysis on the Solidity codebase. This process flags functions that allow unauthorized state changes and identifies incorrect permission logic early in the development lifecycle.