TW
Tripwire
Find contracts. Test them. Review real vulns.
Contract
0x5a165b5223200a52a2e0286742aec6ab0e47bd93 checked chain 1
Latest run: 019b3836-34c1-7252-95ba-17c0617412e1 complete
Dedaub
Queue = batch runner. Audit = immediate run. Audit + LLM forces codex.
Value & Balances
$310.00
last balance 3 months ago
ETH
0.1000
WETH
0.0000
USDC
0.00
USDT
0.00
Findings Signal
2
confirmed findings
crit 0 high 2 unconfirmed 2 total 4
validated = confirmed for call sinks; sink observed for others

Proxy & Workflow

linkage
Proxy status
non-proxy
Implementation address
—
Proxies pointing here
0
Workflow
checked
attempts 1
checked 1 week ago

Latest Findings

validated = confirmed for call sinks; sink observed for others
Severity Tool Title Validated Confirmed
high detector Untrusted CALL target/value reachable yes yes
high detector ETH value transfer possible yes yes
Show unconfirmed findings
Severity Tool Title Validated Confirmed
low codex `transfer(address,uint256)` is non-standard and appears to return no boolean no —
low codex Contract accepts ETH but bytecode shows no recovery path, so sent ETH can be trapped no —
From run 019b3836-34c1-7252-95ba-17c0617412e1 confirmed 2

Codex

latest run
complete bytecode findings
Bytecode appears to be a minimal non-upgradeable token with inferred selectors `name()`, `symbol()`, `decimals()`, `balanceOf(address)`, and `transfer(address,uint256)`. I did not find evidence of delegatecall, proxy sto...
Top findings
  • low `transfer(address,uint256)` is non-standard and appears to return no boolean
  • low Contract accepts ETH but bytecode shows no recovery path, so sent ETH can be trapped
View run

Code Metadata

fingerprint
Created block
1160396
Code size
713
Codehash
0x000d13dda2843fe929be00661f96552e3f1e851c177f0c270f65088f35b0c09b
Priority score
310.000000

Recent Runs

last 20
Run ID Status Validated Total findings Created
019b3836-34c1-7252-95ba-17c0617412e1 complete crit 0 high 2 4 3 months ago