weasel-poc

To write a proof-of-concept exploit, you provide the vulnerability type and target contract details to generate testable Solidity PoC code. This produces reproducible PoC code that proves a vulnerability and integrates into existing test suites.

Yes, you can generate PoC exploit tests that work with Foundry or Hardhat. The generated PoC tests are placed in standard project test files and executed using your project's standard test command like forge test or npx hardhat test.

You need to provide a Solidity project with a test harness, a vulnerability description, and an existing repository structure. These inputs allow the tool to place and run the PoC tests deterministically within your current development environment.

The best way to demonstrate smart contract security issues is by generating testable proof-of-concept exploits. This approach demonstrates security issues with deterministic tests rather than descriptive reports, allowing auditors to verify impact directly.

You add a minimal PoC by generating ready-to-run exploit code and placing the new test in a file like test/Vault.t.sol. Running your project's standard test command then executes the PoC to illustrate and verify the attack scenario.

Yes, generating PoC exploits requires an existing repository structure along with a Solidity project and test harness. The tool places and runs the PoC tests within this existing structure to ensure deterministic and reproducible outputs.