Defi Malicious
by defi.hugen.tokyo in Onchain & crypto
Check if a wallet is flagged as malicious — query multiple security databases for known scammers, exploit attackers, rug pull deployers, and sanctioned entities. Returns classification tag and risk level. No API keys needed. Accepts USDC payments on Base and Solana
https://defi.hugen.tokyo/defi/malicious- Price
- $0.01
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 873 ms
- 997 ms slowest 5%
- Last check
- Passed
- 1 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://defi.hugen.tokyo/defi/malicious
Each call costs $0.01 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
GET https://defi.hugen.tokyo/defi/malicious?address=0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045Example response
The provider's example. We can't check it without paying.
{
"is_malicious_address": false,
"malicious_behavior": [
"none"
],
"tag": "safe"
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.01.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://defi.hugen.tokyo/defi/malicious?address=0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://defi.hugen.tokyo/defi/malicious?address=0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fdefi.hugen.tokyo%2Fdefi%2Fmalicious
const res = await pay("https://defi.hugen.tokyo/defi/malicious?address=0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://defi.hugen.tokyo/defi/malicious?address=0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 1 h ago | Passed | 402 | 876 ms | $0.01 |
| 7 h ago | Passed | 402 | 911 ms | $0.01 |
| 12 h ago | Passed | 402 | 873 ms | $0.01 |
| 17 h ago | Passed | 402 | 861 ms | $0.01 |
| 22 h ago | Passed | 402 | 893 ms | $0.01 |
Show 10 older checks
| 27 h ago | Passed | 402 | 874 ms | $0.01 |
| 32 h ago | Passed | 402 | 837 ms | $0.01 |
| 37 h ago | Passed | 402 | 854 ms | $0.01 |
| 42 h ago | Passed | 402 | 335 ms | $0.01 |
| 46 h ago | Passed | 402 | 997 ms | $0.01 |
| 2 days ago | Passed | 402 | 863 ms | $0.01 |
| 2 days ago | Passed | 402 | 857 ms | $0.01 |
| 3 days ago | Passed | 402 | 943 ms | $0.01 |
| 3 days ago | Passed | 402 | 875 ms | $0.01 |
| 3 days ago | Passed | 402 | 878 ms | $0.01 |