Detect access control and upgradeability vulnerabilities in Solidity smart contracts.
npx skills add https://github.com/n4igme/randscript --skill vuln-web3-access
Please help me install this Agent Skill. Skill: vuln-web3-access Source: https://github.com/n4igme/randscript/tree/main/llm/skills/scode/vuln-web3-access Command: npx skills add https://github.com/n4igme/randscript --skill vuln-web3-access
This skill helps security teams automatically identify access control flaws and unsafe upgrade patterns in smart contracts, reducing manual review time and improving audit quality.
Provide threat-model and recon data, then run the scanner to append findings to ./assessment/vulnerabilities.md.
High-intent search queries and answers about installing and using this skill.
To scan Solidity smart contracts for access control vulnerabilities, provide threat-model and recon data to the scanner. It identifies missing modifiers, tx.origin usage, and unprotected initializers, then appends findings to ./assessment/vulnerabilities.md.
Common upgradeability and proxy storage risks include storage-slot conflicts and improper upgrade patterns that enable takeover. The scanner detects these flaws by assessing proxy storage layouts and checking if upgrade authorization and admin roles are securely managed.
Yes, you can use this scanner for bug bounty and security audit workflows. It applies to Solidity projects across these workflows by parsing threat-model inputs, detecting unsafe access control patterns, and guiding the mapping of findings to vulnerability reports.
To detect missing onlyOwner modifiers and unprotected initializers in Solidity, the scanner parses smart contract code for functions lacking proper access control and initialize functions callable by anyone without initialization guards.
Running a smart contract vulnerability assessment requires threat-model and recon data as input. The scanner uses this data to identify access control flaws and unsafe upgrade patterns, writing the results directly to ./assessment/vulnerabilities.md.
Using tx.origin for authentication creates a vulnerability because it can be spoofed by intermediary contracts. The scanner detects tx.origin usage in authentication logic to flag this access control weakness during security audits.
n4igmeConvert recon data into STRIDE threat models and attack trees.
dapperdiversGenerate structured markdown penetration test reports from JSON security scan findings.
ArianHobson333Audit Solidity smart contracts for reentrancy and EVM vulnerabilities using Slither and Foundry.
huangwb8Identify and mitigate security risks through threat modeling and compliance checks.
