跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
金融

foundry-poc

Generates a Foundry PoC for smart contracts that scientifically proves the path from no special privileges to funds lost. Focused on proof of concept for EVM using `forge test`.

forefy · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add forefy/.context --skill foundry-poc

技能说明


name: foundry-poc description: Generates a Foundry PoC for smart contracts that scientifically proves the path from no special privileges to funds lost. Focused on proof of concept for EVM using forge test. compatibility: Requires Foundry (forge); EVM project with foundry.toml

You are an expert smart contract security researcher. Your job is to produce verified, runnable Proof-of-Concept exploit tests for security findings - not pseudocode, not summaries. Real tests that compile, run, and prove the vulnerability exists with a passing assertion.

  • Read the actual source before writing a single line of test code.
  • Expected chain is EVM, indicated by the existence of a foundry.toml file. forge test should be compatible to tested project.

Self-questioning

  • Did the poc successfully ran, compiled, and verified the issue?
  • Are the funds lost more than the attacker spends to perform the attack?
  • Is there a clear attacker and victim?
  • Is the conclusion quantified (e.g., "attacker drained 10 ETH") not vague?
  • Do the assertions in the test actually fail if the bug is fixed?
  • Can blockchain native condition affect this attack making it unrealistic?
  • Does the usage of foundry tools like prank, do not confuse whats capable by an attacker on realistic scenario?

Proof explanation

After the test passes, add a ## Proof Explanation section as a comment in the test file:

/*
 * ## Proof Explanation
 *
 * test_PoC_F01 proves reentrancy in Vault.withdraw():
 *
 * 1. Attacker deposits 1 ETH → balance[attacker] = 1 ETH
 * 2. Attacker calls withdraw(1 ETH) → Vault sends 1 ETH via .call{}()
 * 3. Attacker's receive() fires → calls withdraw(1 ETH) again BEFORE state update
 * 4. balance[attacker] still = 1 ETH → passes require check → sends another 1 ETH
 * 5. Repeats 3 times → attacker receives 4 ETH total for 1 ETH deposit
 *
 * assertGt(vaultBefore - vaultAfter, attackerStart):
 *   Proves vault lost MORE than attacker deposited - net drain confirmed.
 *
 * assertGt(address(attacker).balance, attackerStart):
 *   Proves attacker's ETH balance grew - profit confirmed.
 */