TW
Tripwire
Find contracts. Test them. Review real vulns.
Contract
0x08b54d4f5877ee091e31e92523b9791df9efce93 checked chain 1
Latest run: 019b3836-356e-733b-b631-4f1e1b0cfb47 complete
Dedaub
Queue = batch runner. Audit = immediate run. Audit + LLM forces codex.
Value & Balances
$12.40
last balance 3 months ago
ETH
0.0040
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 Contract appears to accept ETH but exposes no visible recovery path no —
low codex Legacy silent-success semantics can mislead integrations no —
From run 019b3836-356e-733b-b631-4f1e1b0cfb47 confirmed 2

Codex

latest run
complete bytecode findings
I reviewed `BYTECODE_BUNDLE.json` and the runtime looks like a small legacy ERC20-like token with inferred selectors `name`, `symbol`, `decimals`, `balanceOf`, and `transfer`. I did not treat the detector's `CALL` findin...
Top findings
  • low Contract appears to accept ETH but exposes no visible recovery path
  • low Legacy silent-success semantics can mislead integrations
View run

Code Metadata

fingerprint
Created block
1178895
Code size
713
Codehash
0x000d13dda2843fe929be00661f96552e3f1e851c177f0c270f65088f35b0c09b
Priority score
12.400000

Recent Runs

last 20
Run ID Status Validated Total findings Created
019b3836-356e-733b-b631-4f1e1b0cfb47 complete crit 0 high 2 4 3 months ago