passlisted in Coinbase#7 by calls of 11 on this host
0.01 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 2
- Unique payers, trailing 30 days
- 2
- Last called
- 2026-10-08 06:26 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.01 USDC
- Networks
- 2
How has the volume on this endpoint moved?
defi.hugen.tokyo lists 11 endpoints; defi malicious is tied 7th by calls with 1 other.
The listing describes the request as the query parameter address.
defi malicious returns json; the example shows tag, malicious_behavior and is_malicious_address.
The registry's counters give defi malicious 2 calls and 2 unique payers over 30 days, every call from a different payer.
The last call to defi malicious came 24 days before the snapshot, 2026-10-08.
A call to defi malicious costs 0.01 USDC on Base, as declared.
Of the calls counted across defi.hugen.tokyo, defi malicious takes 1%.
Payment is declared 2 ways across 2 networks: Base and Solana, to 2 different wallets.
TOLL files defi malicious under market data: a GET endpoint on defi.hugen.tokyo, listed in the Coinbase registry.
defi malicious answered the sweep of 2026-10-31 with a valid 402, as at every sweep since 2026-09-11.
Closest in price to defi malicious within market data: token price at api.kadec0.xyz and address current balance at api.nansen.ai.
defi malicious is priced above 47% of comparable listings in market data.
The wallet paid by defi malicious is the payee of 72 endpoints across 12 hosts.
The seller's tags on defi malicious are defi, security, bridge and tvl, and its label is "defi".
The price of defi malicious is declared by 2,244 other listings in market data too.
the payment options, as of 2026-11-01 05:59 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.01 USDC | exact | 0x29322E…2E4f60 |
| Coinbase | solana: | USDC | 0.01 USDC | exact | 4du4Afkj…boaS5Z |
the checks, as of 2026-10-31 10:30 UTC · method · pinnableendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-31 10:30 UTC | pass | 0 | daily-2026-10-31 |
| 2026-10-30 05:53 UTC | pass | 0 | daily-2026-10-30 |
| 2026-10-29 05:35 UTC | pass | 0 | daily-2026-10-29 |
| 2026-10-28 05:58 UTC | pass | 0 | daily-2026-10-28 |
| 2026-10-27 05:54 UTC | pass | 0 | daily-2026-10-27 |
| 2026-10-26 05:49 UTC | pass | 0 | daily-2026-10-26 |
| 2026-10-24 20:36 UTC | pass | 0 | daily-2026-10-24 |
| 2026-10-23 05:44 UTC | pass | 0 | daily-2026-10-23 |
| 2026-10-22 03:59 UTC | pass | 0 | daily-2026-10-22 |
| 2026-10-21 07:23 UTC | pass | 0 | daily-2026-10-21 |
| 2026-10-20 07:18 UTC | pass | 0 | daily-2026-10-20 |
| 2026-10-19 05:25 UTC | pass | 0 | daily-2026-10-19 |
| 2026-10-18 07:44 UTC | pass | 0 | daily-2026-10-18 |
| 2026-10-17 17:40 UTC | pass | 0 | daily-2026-10-17 |
| 2026-10-16 03:58 UTC | pass | 0 | daily-2026-10-16 |
| 2026-10-15 05:31 UTC | pass | 0 | daily-2026-10-15 |
| 2026-10-14 03:57 UTC | pass | 0 | daily-2026-10-14 |
| 2026-10-13 08:20 UTC | pass | 0 | daily-2026-10-13 |
| 2026-10-12 05:41 UTC | pass | 0 | daily-2026-10-12 |
| 2026-10-11 04:00 UTC | pass | 0 | daily-2026-10-11 |
| 2026-10-10 09:06 UTC | pass | 0 | daily-2026-10-10 |
| 2026-10-09 04:01 UTC | pass | 0 | daily-2026-10-09 |
| 2026-10-08 05:33 UTC | pass | 0 | daily-2026-10-08 |
| 2026-10-07 04:05 UTC | pass | 0 | daily-2026-10-07 |
| 2026-10-06 05:39 UTC | pass | 0 | daily-2026-10-06 |
| 2026-10-05 05:19 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-04 08:30 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-03 03:55 UTC | pass | 0 | daily-2026-10-03 |
| 2026-10-02 13:04 UTC | pass | 0 | daily-2026-10-02 |
| 2026-10-01 06:20 UTC | pass | 0 | daily-2026-10-01 |
| 2026-09-30 05:39 UTC | pass | 0 | daily-2026-09-30 |
| 2026-09-29 17:59 UTC | pass | 0 | daily-2026-09-29 |
| 2026-09-28 03:53 UTC | pass | 0 | daily-2026-09-28 |
| 2026-09-25 19:35 UTC | pass | 0 | daily-2026-09-25 |
| 2026-09-23 05:18 UTC | pass | 0 | daily-2026-09-23 |
| 2026-09-22 05:27 UTC | pass | 0 | daily-2026-09-22 |
| 2026-09-21 05:51 UTC | pass | 0 | daily-2026-09-21 |
| 2026-09-20 18:31 UTC | pass | 0 | daily-2026-09-20 |
| 2026-09-19 03:53 UTC | pass | 0 | daily-2026-09-19 |
| 2026-09-18 08:44 UTC | pass | 0 | daily-2026-09-18 |
| 2026-09-17 03:53 UTC | pass | 0 | daily-2026-09-17 |
| 2026-09-16 03:52 UTC | pass | 0 | daily-2026-09-16 |
| 2026-09-15 03:52 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 03:52 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 03:52 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 06:06 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 09:30 UTC | pass | 0 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-10-08 06:26 UTC · method · live
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
}
},
"output": {
"type": "json",
"example": {
"tag": "safe",
"malicious_behavior": [
"none"
],
"is_malicious_address": false
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-11-01 05:59 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "defi malicious on defi.hugen.tokyo", snapshot of 2026-11-01 05:59 UTC. https://tollindex.com/e/defi-hugen-tokyo-defi-malicious-06e3e5/at/2026-11-01T05-59Z. Accessed [access date].
BibTeX
@misc{toll-e-defi-hugen-tokyo-defi-malicious-06e3e5-2026-11-01T05-59Z,
author = {TOLL},
title = {defi malicious on defi.hugen.tokyo},
howpublished = {\url{https://tollindex.com/e/defi-hugen-tokyo-defi-malicious-06e3e5/at/2026-11-01T05-59Z}},
year = {2026},
month = {11},
note = {Pinned view of the snapshot of 2026-11-01 05:59 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.