
Smart Contract Vulnerabilities
- 2.2k installs
- 1.5k repo stars
- Updated June 16, 2026
- yaklang/hack-skills
smart-contract-vulnerabilities is an agent skill that Smart contract vulnerability playbook. Use when auditing Solidity/EVM contracts for reentrancy, integer overflow, access control, delegatecall, flash loan, signature
About
The smart-contract-vulnerabilities skill. Smart contract vulnerability playbook. Use when auditing Solidity/EVM contracts for reentrancy, integer overflow, access control, delegatecall, flash loan, signature replay, and MEV-related attack patterns. Covers reentrancy (single, cross-function, cross-contract, read-only), integer overflow, access control, delegatecall, randomness manipulation, flash loans, signature replay, front-running/MEV, and CREATE2 exploitation. Base models miss subtle cross-contract reentrancy and storage layout collisions in proxy patterns. REENTRANCY The most iconic smart contract vulnerability. External calls transfer execution control; if state is not updated before the call, the callee can re-enter. Especially dangerous in DeFi protocols where multiple contracts share state. No state modification in the victim, but the stale intermediate state misleads the reader. The workflow follows the source SKILL.md contract with progressive reference loading, clear trigger phrases, and practical steps developers can apply directly in agent sessions.
- [defi-attack-patterns](../defi-attack-patterns/SKILL.md) when the vulnerability is part of a DeFi protocol exploit (flas
- [deserialization-insecure](../deserialization-insecure/SKILL.md) when the target is off-chain infrastructure deserializi
- Side-by-side vulnerable vs fixed code patterns for each vulnerability class
- Gas optimization traps that introduce vulnerabilities
- Proxy pattern storage collision examples with slot calculations
Smart Contract Vulnerabilities by the numbers
- 2,231 all-time installs (skills.sh)
- +125 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #17 of 479 Web3 & Blockchain skills by installs in the Skillselion catalog
- Security screen: CRITICAL risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
smart-contract-vulnerabilities capabilities & compatibility
- Capabilities
- [defi attack patterns](../defi attack patterns/s · [deserialization insecure](../deserialization in · side by side vulnerable vs fixed code patterns f · gas optimization traps that introduce vulnerabil · proxy pattern storage collision examples with sl
- Use cases
- security audit · testing · debugging
What smart-contract-vulnerabilities says it does
Base models miss subtle cross-contract reentrancy and storage layout collisions in proxy patterns.
REENTRANCY The most iconic smart contract vulnerability.
npx skills add https://github.com/yaklang/hack-skills --skill smart-contract-vulnerabilitiesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2.2k |
|---|---|
| repo stars | ★ 1.5k |
| Security audit | 1 / 3 scanners passed |
| Last updated | June 16, 2026 |
| Repository | yaklang/hack-skills ↗ |
How do I apply smart-contract-vulnerabilities correctly using the SKILL.md workflows and reference files?
Smart contract vulnerability playbook. Use when auditing Solidity/EVM contracts for reentrancy, integer overflow, access control, delegatecall, flash loan, signature replay, and MEV-related attack pat
Who is it for?
Developers and software engineers working with smart-contract-vulnerabilities patterns from the skill documentation.
Skip if: Skip when cached docs are empty, boilerplate-only, or outside the skill documented scope.
When should I use this skill?
Smart contract vulnerability playbook. Use when auditing Solidity/EVM contracts for reentrancy, integer overflow, access control, delegatecall, flash loan, signature replay, and MEV-related attack patterns.
What you get
Grounded smart-contract-vulnerabilities guidance with highlights, triggers, and evidence quotes from SKILL.md.
- Vulnerability audit checklist
- Prioritized security findings
Files
SKILL: Smart Contract Vulnerabilities — Expert Attack Playbook
AI LOAD INSTRUCTION: Expert smart contract audit techniques. Covers reentrancy (single, cross-function, cross-contract, read-only), integer overflow, access control, delegatecall, randomness manipulation, flash loans, signature replay, front-running/MEV, and CREATE2 exploitation. Base models miss subtle cross-contract reentrancy and storage layout collisions in proxy patterns.
0. RELATED ROUTING
- defi-attack-patterns when the vulnerability is part of a DeFi protocol exploit (flash loans, oracle manipulation, governance attacks)
- deserialization-insecure when the target is off-chain infrastructure deserializing blockchain data
Advanced Reference
Also load SOLIDITY_VULN_PATTERNS.md when you need:
- Side-by-side vulnerable vs fixed code patterns for each vulnerability class
- Gas optimization traps that introduce vulnerabilities
- Proxy pattern storage collision examples with slot calculations
---
1. REENTRANCY
The most iconic smart contract vulnerability. External calls transfer execution control; if state is not updated before the call, the callee can re-enter.
1.1 Classic Reentrancy (Single-Function)
Victim.withdraw()
├── checks balance[msg.sender] > 0 ✓
├── msg.sender.call{value: balance}("") ← external call
│ └── Attacker.receive()
│ └── Victim.withdraw() ← re-enters before state update
│ ├── checks balance[msg.sender] ← still > 0!
│ └── sends ETH again
└── balance[msg.sender] = 0 ← too late1.2 Cross-Function Reentrancy
Two functions share state; attacker re-enters a different function during callback:
| Step | Execution | State |
|---|---|---|
| 1 | Call withdraw() → external call | balance still positive |
| 2 | Attacker fallback calls transfer(attacker2) | balance used before reset |
| 3 | transfer reads stale balance → moves funds | attacker2 receives tokens |
| 4 | Original withdraw completes, zeroes balance | damage done |
1.3 Cross-Contract Reentrancy
Contract A calls Contract B, which calls back into Contract A (or Contract C that reads A's stale state). Especially dangerous in DeFi protocols where multiple contracts share state.
1.4 Read-Only Reentrancy
The re-entered function is a view function used by a third-party contract for price calculation. No state modification in the victim, but the stale intermediate state misleads the reader.
Real-world: Curve pool get_virtual_price() read during remove_liquidity() callback → inflated price → profit on dependent lending protocol.
Mitigations
| Pattern | Protection Level |
|---|---|
| Checks-Effects-Interactions (CEI) | Core defense; update state before external call |
ReentrancyGuard (OpenZeppelin) | Mutex lock; prevents same-tx re-entry |
| Pull payment pattern | Eliminate external calls in state-changing functions |
| CEI + guard on all public functions | Defense-in-depth against cross-function |
---
2. INTEGER OVERFLOW / UNDERFLOW
Pre-Solidity 0.8
Arithmetic silently wraps: uint8(255) + 1 == 0, uint8(0) - 1 == 255.
| Attack | Example |
|---|---|
| Balance underflow | balances[attacker] -= amount when amount > balance → huge balance |
| Supply overflow | totalSupply + mintAmount wraps → bypass cap checks |
| Timelock bypass | lockTime[msg.sender] + extend wraps to past → early unlock |
Post-Solidity 0.8
Default checked arithmetic reverts on overflow. But unchecked{} blocks reintroduce risk:
unchecked {
// "gas optimization" — but if i can be influenced by user input, overflow returns
for (uint i = start; i < end; i++) { ... }
}SafeMath Bypass Scenarios
- Casting:
uint256→uint128truncation before SafeMath check - Assembly blocks:
mstore/addbypass Solidity-level checks - Intermediate multiplication overflow before division:
(a * b) / cwherea * boverflows
---
3. ACCESS CONTROL
tx.origin vs msg.sender
| Property | msg.sender | tx.origin |
|---|---|---|
| Value | Immediate caller | EOA that initiated the tx |
| Safe for auth | Yes | No — phishing contract can inherit tx.origin |
Attack: trick owner into calling attacker contract → attacker contract calls victim with owner's tx.origin.
Common Patterns
| Issue | Impact |
|---|---|
Missing onlyOwner on critical functions | Anyone can call admin functions |
Unprotected selfdestruct | Anyone can destroy the contract, force-send ETH |
Unprotected delegatecall | Attacker executes arbitrary code in victim's context |
| Default visibility (pre-0.6.0) | Functions default to public |
| Missing zero-address checks | Ownership transferred to address(0) |
---
4. RANDOMNESS MANIPULATION
On-chain randomness sources are predictable to miners/validators:
| Source | Predictability |
|---|---|
block.timestamp | Miner has ~15s window to manipulate |
blockhash(block.number - 1) | Known to all at execution time |
blockhash(block.number) | Always returns 0 (current block hash unknown) |
block.difficulty / block.prevrandao | Post-merge: known beacon chain value |
Commit-reveal bypass: If reveal phase doesn't enforce timeout or bond, attacker can choose not to reveal unfavorable outcomes (selective abort attack).
---
5. DELEGATECALL VULNERABILITIES
delegatecall executes callee's code in caller's storage context. Storage slot layout must match exactly.
Storage Layout Collision
Proxy (storage): Implementation (code):
slot 0: owner slot 0: someVariable
slot 1: implementation slot 1: anotherVariableImplementation writes to someVariable (slot 0) → overwrites proxy's owner. Attacker calls implementation function that writes slot 0 → becomes proxy owner.
Function Selector Collision
4-byte function selectors can collide. If proxy's admin() selector collides with implementation's transfer(), calling admin() on the proxy executes transfer() logic.
Tool: cast selectors <bytecode> (Foundry) to enumerate selectors.
---
6. FRONT-RUNNING / MEV
Transaction Ordering Manipulation
Victim submits DEX swap tx (visible in mempool)
├── Front-runner: buy token before victim (raise price)
├── Victim tx executes at worse price
└── Back-runner: sell token after victim (profit from spread)
= Sandwich attackProtection Patterns
| Defense | Mechanism |
|---|---|
| Commit-reveal | Hide transaction intent until reveal |
| Flashbots / private mempool | Submit tx directly to block builder |
| Slippage protection | Set minAmountOut to limit MEV extraction |
| Time-lock | Delay execution to reduce predictability |
---
7. SIGNATURE REPLAY
Missing Nonce
Reuse a valid signature to repeat the action (e.g., transfer) multiple times.
Cross-Chain Replay
Same contract deployed on multiple chains with same address → signature valid on all chains. Must include block.chainid in signed message.
EIP-712 Implementation Errors
| Error | Consequence |
|---|---|
Missing DOMAIN_SEPARATOR with chainId | Cross-chain replay |
| Domain separator cached at deploy | Breaks after hard fork changing chainId |
| Missing nonce in struct hash | Signature replay |
ecrecover returns address(0) on invalid sig | Passes == address(0) owner check |
---
8. SELF-DESTRUCT & FORCE-SEND ETH
selfdestruct(recipient) force-sends all contract ETH to recipient — bypasses receive() and fallback(), cannot be rejected.
Breaks contracts that rely on address(this).balance for logic (e.g., require(balance == expected)).
Post-EIP-6780 (Dencun): selfdestruct only sends ETH; code/storage deletion only if called in same tx as creation.
---
9. CREATE2 & DETERMINISTIC ADDRESS EXPLOITATION
CREATE2 address = keccak256(0xff ++ deployer ++ salt ++ keccak256(initCode)).
| Attack | Method |
|---|---|
| Pre-fund exploitation | Predict address → send tokens/ETH before deployment → selfdestruct → redeploy different code at same address |
| Pre-approve exploitation | Predicted address gets token approvals → deploy malicious contract → drain approved tokens |
| Metamorphic contracts | CREATE2 → selfdestruct → CREATE2 with same salt but different initCode (pre-EIP-6780) |
---
10. FLASH LOAN ATTACK PATTERNS
Single transaction:
├── Borrow large amount (no collateral)
├── Manipulate state (price oracle, governance, etc.)
├── Extract profit from manipulated state
├── Repay loan + fee
└── Keep profitKey: entire sequence must succeed atomically or the whole tx reverts.
---
11. SHORT ADDRESS ATTACK
EVM pads missing bytes in ABI-encoded calldata with zeros. If transfer(address, uint256) is called with a 19-byte address, the uint256 amount shifts left by 8 bits → multiplied by 256.
Mitigation: validate calldata length; modern Solidity compilers add checks.
---
12. TOOLS
| Tool | Purpose | Usage |
|---|---|---|
| Slither | Static analysis, vulnerability detection | slither . in project root |
| Mythril | Symbolic execution, path exploration | myth analyze contract.sol |
| Echidna | Property-based fuzzing | Define invariants, fuzz for violations |
| Foundry (Forge) | Test framework, fuzzing, gas analysis | forge test --fuzz-runs 10000 |
| Hardhat | Development, testing, deployment | npx hardhat test |
| Certora | Formal verification | Write specs, prove/disprove properties |
| 4naly3er | Automated gas optimization + vuln report | CI integration |
---
13. DECISION TREE
Auditing a smart contract?
├── Is it a proxy pattern?
│ ├── Yes → Check storage layout collision (Section 5)
│ │ ├── Compare slot assignments between proxy and implementation
│ │ ├── Check for function selector collision
│ │ └── Verify initializer cannot be called twice
│ └── No → Continue
├── Does it make external calls?
│ ├── Yes → Check reentrancy (Section 1)
│ │ ├── State updated before call? → CEI pattern OK
│ │ ├── ReentrancyGuard present? → Check all entry points
│ │ ├── Cross-function state sharing? → Cross-function reentrancy risk
│ │ └── View functions read during callback? → Read-only reentrancy
│ └── No → Continue
├── Does it handle tokens/ETH?
│ ├── Yes → Check integer overflow (Section 2)
│ │ ├── Solidity < 0.8? → All arithmetic suspect
│ │ ├── unchecked{} blocks? → Verify no user-influenced values
│ │ └── Casting between uint sizes? → Truncation risk
│ └── Also check self-destruct force-send (Section 8)
├── Does it use signatures?
│ ├── Yes → Check replay (Section 7)
│ │ ├── Nonce included? → Verify incremented
│ │ ├── ChainId included? → Cross-chain safe
│ │ └── ecrecover result checked for address(0)? → OK
│ └── No → Continue
├── Does it use on-chain randomness?
│ ├── Yes → Predictable (Section 4)
│ │ └── Recommend Chainlink VRF or commit-reveal with bond
│ └── No → Continue
├── Does it interact with DeFi protocols?
│ ├── Yes → Load [defi-attack-patterns](../defi-attack-patterns/SKILL.md)
│ │ ├── Flash loan vectors
│ │ ├── Oracle manipulation
│ │ └── MEV exposure
│ └── No → Continue
├── Does it use CREATE2?
│ ├── Yes → Check deterministic address exploitation (Section 9)
│ └── No → Continue
└── Run automated tools (Section 12)
├── Slither for static analysis
├── Mythril for symbolic execution
└── Echidna for fuzzing invariantsSolidity Vulnerability Patterns — Code Reference
Load trigger: When the agent needs side-by-side vulnerable vs fixed Solidity code patterns, gas-optimization-introduced vulnerabilities, or proxy storage slot collision calculations. Assumes the main SKILL.md is already loaded for conceptual understanding.
---
1. REENTRANCY — VULNERABLE VS FIXED
1.1 Classic Reentrancy
Vulnerable:
function withdraw() public {
uint bal = balances[msg.sender];
require(bal > 0);
(bool sent, ) = msg.sender.call{value: bal}("");
require(sent, "Failed to send");
balances[msg.sender] = 0; // state update AFTER external call
}Fixed (Checks-Effects-Interactions):
function withdraw() public {
uint bal = balances[msg.sender];
require(bal > 0);
balances[msg.sender] = 0; // state update BEFORE external call
(bool sent, ) = msg.sender.call{value: bal}("");
require(sent, "Failed to send");
}1.2 Cross-Function Reentrancy
Vulnerable:
function withdraw() public {
uint bal = balances[msg.sender];
require(bal > 0);
(bool sent, ) = msg.sender.call{value: bal}("");
require(sent);
balances[msg.sender] = 0;
}
function transfer(address to, uint amount) public {
require(balances[msg.sender] >= amount);
balances[msg.sender] -= amount;
balances[to] += amount;
}
// Attacker: during withdraw callback, call transfer() with stale balanceFixed:
import "@openzeppelin/contracts/security/ReentrancyGuard.sol";
contract Safe is ReentrancyGuard {
function withdraw() public nonReentrant { ... }
function transfer(address to, uint amount) public nonReentrant { ... }
}1.3 Read-Only Reentrancy
Vulnerable third-party contract:
function getPrice() external view returns (uint) {
return pool.get_virtual_price(); // reads stale state during pool callback
}
function deposit(uint amount) external {
uint price = getPrice(); // inflated during reentrancy window
uint shares = amount * 1e18 / price;
_mint(msg.sender, shares); // mints too few shares (or too many)
}Attacker contract:
function attack() external {
pool.remove_liquidity(...); // triggers callback
}
receive() external payable {
// During callback: pool state is intermediate
// get_virtual_price() returns inflated value
vulnerableProtocol.deposit{value: 1 ether}(1 ether);
}---
2. INTEGER OVERFLOW / UNDERFLOW
2.1 Pre-0.8 Balance Underflow
Vulnerable (Solidity < 0.8):
pragma solidity ^0.7.0;
function transfer(address to, uint256 amount) public {
require(balances[msg.sender] - amount >= 0); // always true for uint!
balances[msg.sender] -= amount; // underflows to ~2^256
balances[to] += amount;
}Fixed:
pragma solidity ^0.7.0;
import "@openzeppelin/contracts/math/SafeMath.sol";
function transfer(address to, uint256 amount) public {
balances[msg.sender] = balances[msg.sender].sub(amount); // reverts on underflow
balances[to] = balances[to].add(amount);
}2.2 Timelock Bypass via Overflow
Vulnerable:
function increaseLockTime(uint _seconds) public {
lockTime[msg.sender] += _seconds; // overflow wraps to small value
}
function withdraw() public {
require(block.timestamp > lockTime[msg.sender]);
// ...
}
// Attack: increaseLockTime(type(uint256).max - lockTime + 1) → wraps to 02.3 Unsafe Casting (Post-0.8 Risk)
function processAmount(uint256 amount) external {
uint128 truncated = uint128(amount); // 0.8 does NOT revert on downcast!
// amount = 2^128 + 1 → truncated = 1
_transfer(msg.sender, truncated);
}Fixed (Solidity ≥ 0.8.0):
function processAmount(uint256 amount) external {
require(amount <= type(uint128).max, "overflow");
uint128 safe = uint128(amount);
_transfer(msg.sender, safe);
}---
3. ACCESS CONTROL
3.1 tx.origin Phishing
Vulnerable:
function transferOwnership(address newOwner) public {
require(tx.origin == owner); // tx.origin = EOA, not immediate caller
owner = newOwner;
}Attack contract:
contract PhishingAttack {
VulnerableContract target;
function attack() external {
// If the owner calls this function (tricked via phishing link),
// tx.origin == owner → passes the check
target.transferOwnership(address(this));
}
}Fixed:
function transferOwnership(address newOwner) public {
require(msg.sender == owner); // msg.sender = immediate caller
owner = newOwner;
}3.2 Unprotected Selfdestruct
Vulnerable:
function destroy() external {
selfdestruct(payable(msg.sender)); // no access control
}3.3 Unprotected Initializer (Proxy Pattern)
Vulnerable:
function initialize(address _owner) public {
owner = _owner; // can be called by anyone, multiple times
}Fixed:
import "@openzeppelin/contracts-upgradeable/proxy/utils/Initializable.sol";
function initialize(address _owner) public initializer {
owner = _owner;
}---
4. DELEGATECALL STORAGE COLLISION
4.1 Proxy-Implementation Slot Mismatch
// Proxy contract
contract Proxy {
address public implementation; // slot 0
address public owner; // slot 1
fallback() external payable {
(bool s, ) = implementation.delegatecall(msg.data);
require(s);
}
}
// Implementation contract
contract Implementation {
uint public someValue; // slot 0 — COLLIDES with Proxy.implementation!
address public admin; // slot 1 — COLLIDES with Proxy.owner!
function setSomeValue(uint _val) public {
someValue = _val; // overwrites Proxy.implementation address!
}
}Fixed (EIP-1967 storage slots):
contract SafeProxy {
// Implementation stored at keccak256("eip1967.proxy.implementation") - 1
bytes32 private constant IMPL_SLOT =
0x360894a13ba1a3210667c828492db98dca3e2076cc3735a920a3ca505d382bbc;
function _implementation() internal view returns (address impl) {
assembly { impl := sload(IMPL_SLOT) }
}
}4.2 Function Selector Collision in Transparent Proxy
admin() selector: 0xf851a440
collide_func() selector: 0xf851a440 ← same 4 bytes by coincidenceTool to check: cast sig "functionName(argTypes)" computes selector.
---
5. RANDOMNESS MANIPULATION
Vulnerable:
function roll() external payable {
uint random = uint(keccak256(abi.encodePacked(
block.timestamp,
block.difficulty,
msg.sender
))) % 6;
if (random == 0) {
payable(msg.sender).transfer(address(this).balance);
}
}Attack contract:
contract AttackRoll {
function attack(VulnerableRoll target) external payable {
uint random = uint(keccak256(abi.encodePacked(
block.timestamp,
block.difficulty,
address(this)
))) % 6;
require(random == 0, "not winning, skip");
target.roll{value: msg.value}();
}
}---
6. SIGNATURE REPLAY
Vulnerable:
function executeWithSig(address to, uint amount, bytes memory sig) external {
bytes32 hash = keccak256(abi.encodePacked(to, amount));
address signer = ECDSA.recover(hash, sig);
require(signer == owner, "invalid sig");
// no nonce → same signature can be replayed
payable(to).transfer(amount);
}Fixed:
mapping(uint256 => bool) public usedNonces;
function executeWithSig(
address to, uint amount, uint256 nonce, bytes memory sig
) external {
require(!usedNonces[nonce], "nonce used");
bytes32 hash = keccak256(abi.encodePacked(to, amount, nonce, block.chainid, address(this)));
address signer = ECDSA.recover(hash, sig);
require(signer == owner, "invalid sig");
usedNonces[nonce] = true;
payable(to).transfer(amount);
}---
7. SELF-DESTRUCT FORCE-SEND ETH
Vulnerable (balance-dependent logic):
function isGameComplete() public view returns (bool) {
return address(this).balance == 10 ether; // exact balance check
}Attack:
contract ForceEth {
function attack(address target) external payable {
selfdestruct(payable(target));
// forces ETH into target, bypassing receive/fallback
// target.balance now != 10 ether → game logic broken
}
}Fixed:
uint public deposits; // track deposits explicitly, don't rely on balance
function isGameComplete() public view returns (bool) {
return deposits == 10 ether;
}---
8. FLASH LOAN ORACLE MANIPULATION
Vulnerable price oracle:
function getPrice(address token) public view returns (uint) {
(uint reserve0, uint reserve1, ) = pair.getReserves();
return reserve0 * 1e18 / reserve1; // spot price — manipulable in same tx
}Attack flow:
1. Flash borrow 10,000 ETH
2. Swap ETH → Token on AMM (crashes token spot price)
3. Call lending protocol that uses spot price → borrow token at deflated price
4. Swap token back → ETH (restore price)
5. Repay flash loan + fee
6. Profit = borrowed tokens at deflated price - flash loan feeFixed (TWAP oracle):
function getPrice(address token) public view returns (uint) {
// Use Uniswap V3 TWAP or Chainlink aggregator
(, int256 price, , uint256 updatedAt, ) = chainlinkFeed.latestRoundData();
require(block.timestamp - updatedAt < 3600, "stale price");
return uint256(price);
}---
9. UNCHECKED RETURN VALUE
Vulnerable:
function withdraw(uint amount) external {
payable(msg.sender).send(amount); // send() returns bool, not checked!
balances[msg.sender] -= amount; // balance decremented even if send failed
}Fixed:
function withdraw(uint amount) external {
(bool success, ) = payable(msg.sender).call{value: amount}("");
require(success, "transfer failed");
balances[msg.sender] -= amount;
}---
10. DENIAL OF SERVICE — UNEXPECTED REVERT
Vulnerable (push pattern):
address[] public recipients;
function distribute() external {
for (uint i = 0; i < recipients.length; i++) {
// If one recipient is a contract that reverts, entire distribution fails
payable(recipients[i]).transfer(1 ether);
}
}Fixed (pull pattern):
mapping(address => uint) public pendingWithdrawals;
function distribute() external {
for (uint i = 0; i < recipients.length; i++) {
pendingWithdrawals[recipients[i]] += 1 ether;
}
}
function withdraw() external {
uint amount = pendingWithdrawals[msg.sender];
pendingWithdrawals[msg.sender] = 0;
payable(msg.sender).transfer(amount);
}---
11. GAS OPTIMIZATION TRAPS
Optimizations that accidentally introduce vulnerabilities:
| Optimization | Vulnerability Introduced |
|---|---|
unchecked{} loop counter | User-controlled bounds → overflow |
Assembly sstore for gas savings | Bypasses Solidity's overflow checks and visibility |
Packed storage (uint128, uint128 in one slot) | Incorrect bit masking → value corruption |
immutable used for mutable config | Cannot update → frozen misconfiguration |
selfdestruct for gas refund | Contract destruction as attack vector (pre-Dencun) |
| Skipping zero-address checks | Gas saved but ownership can be burned |
Related skills
How it compares
Pick smart-contract-vulnerabilities over general code-review skills when the target is EVM bytecode with exploit-focused audit patterns rather than application logic bugs.
FAQ
Who is smart-contract-vulnerabilities for?
Developers and software engineers working with smart-contract-vulnerabilities patterns from the skill documentation.
When should I use smart-contract-vulnerabilities?
Smart contract vulnerability playbook. Use when auditing Solidity/EVM contracts for reentrancy, integer overflow, access control, delegatecall, flash loan, signature replay, and MEV-related attack patterns.
Is smart-contract-vulnerabilities safe to install?
Review the Security Audits panel on this page before installing in production.