- Home
- Skills
- Web3 & Crypto
- evm contract bytecode audit
Works with the AI Agents you already use
evm contract bytecode audit
Audits EVM contract bytecode for honeypots, drainers, and malicious owner patterns before you interact.
$14
evm contract bytecode audit
Example session with this skill installed
Audit this unverified contract on Ethereum at 0x123... to see if it is a honeypot before I buy the token.
- Read your context and instructions
- Compiled the evm contract bytecode
VERDICT: DANGER.
Access: Decompiled bytecode (best-effort).
Findings
- Malicious logic: Internal _transfer function contains a hardcoded blacklist gate.
- Fake Renouncement: renounceOwnership() emits an event but does not zero the owner storage slot.
- EIP-1967: Not detected.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Interacting with unverified or unfamiliar smart contracts is a primary cause of lost funds through honeypots, drainers, and malicious ownership rugs. Standard security scanners often miss these adversarial patterns because they focus on general vulnerabilities rather than intentional fraud.
What it does
- Performs dual-pass analysis using Slither for general vulnerabilities and a custom heuristic suite for honeypot-specific patterns.
- Decompiles unverified bytecode using Heimdall-rs or Dedaub to audit logic even when source code is hidden.
- Detects EIP-1967 proxy patterns, identify upgrade admins, and flag hidden centralization risks.
- Exposes "fake renouncement" scams by auditing the internal logic of ownership transfer functions.
- Categorizes risks into DANGER, SUSPECT, or NO-FINDING verdicts based on exploitability and blast radius.
Frameworks & tools
Slither, Heimdall-rs, Dedaub, EVM, EIP-1967.
Why this beats prompting it yourself
Most LLMs rely on general knowledge that overlooks specific honeypot techniques like fee-on-transfer gates or non-standard proxy implementations. This skill enforces a strict multi-tool workflow that prevents "clean" reports from general scanners being mistaken for a lack of fraud risk.
Use cases
- Audit a new ERC-20 token contract before approving a spend limit or swapping.
- Identify if a minting contract is a drainer before connecting a wallet.
- Verify if a "renounced" contract has hidden backdoors or hardcoded admin overrides.
- Analyze unverified bytecode for malicious logic before an agent interacts with it.
Known limitations
Cannot simulate specific transaction effects like slippage or sandwiching. Does not detect non-standard proxy patterns like Beacon or Diamond proxies. Best-effort reconstruction for unverified code.
Does not simulate specific transaction effects (fees/slippage). Standard proxy checks limited to EIP-1967. Decompiled logic has lower confidence than verified source.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 3 months ago
Permissions
No special permissions declared or detected