Malicious Url
by Vextorium in Security & trust
Check whether a URL or domain is listed in abuse.ch URLhaus as a malware distribution site in the last 30 days: exact URL match and other malicious URLs on the same host, with threat type, online/offline status and date. Use before an agent fetches or opens a link.
https://api.vextorium.com/v1/malicious-url- Price
- $0.002
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 1 h ago, next any minute now
Reliability
Latest check failed 1 h ago: Amount "0.002" is not in atomic token units
How to call it
POST https://api.vextorium.com/v1/malicious-url
Each call costs $0.002 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.
POST https://api.vextorium.com/v1/malicious-url
content-type: application/json
{
"url": "https://example.com"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes |
Example response
The provider's example. We can't check it without paying.
{
"database": {
"updated": "2026-10-03T00:59:28+00:00",
"urls": 15473
},
"exact_match": null,
"examples": [],
"host": "example.com",
"listed": false,
"malicious_urls_on_host": 0,
"online_now": 0,
"query": "https://example.com",
"source": "abuse.ch URLhaus (CC0), URLs from the last 30 days",
"verdict": "not listed"
}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.002.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://api.vextorium.com/v1/malicious-url' \
-H 'content-type: application/json' \
--data-raw '{"url":"https://example.com"}'
# 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 - -X POST 'https://api.vextorium.com/v1/malicious-url' \
-H 'content-type: application/json' \
--data-raw '{"url":"https://example.com"}' \
| 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.002 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.002" });
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.002 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.vextorium.com%2Fv1%2Fmalicious-url&method=POST
const res = await pay("https://api.vextorium.com/v1/malicious-url", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"url": "https://example.com"
}),
});
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.002 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.002"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://api.vextorium.com/v1/malicious-url",
json={
"url": "https://example.com",
},
)
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 | Amount "0.002" is not in atomic token units | 402 | 83 ms | $0.002 |
| 6 h ago | Amount "0.002" is not in atomic token units | 402 | 104 ms | $0.002 |
| 11 h ago | Amount "0.002" is not in atomic token units | 402 | 100 ms | $0.002 |
| 15 h ago | Amount "0.002" is not in atomic token units | 402 | 110 ms | $0.002 |
| 20 h ago | Amount "0.002" is not in atomic token units | 402 | 80 ms | $0.002 |
Show 10 older checks
| 24 h ago | Amount "0.002" is not in atomic token units | 402 | 75 ms | $0.002 |
| 28 h ago | Amount "0.002" is not in atomic token units | 402 | 119 ms | $0.002 |
| 33 h ago | Amount "0.002" is not in atomic token units | 402 | 86 ms | $0.002 |
| 37 h ago | Amount "0.002" is not in atomic token units | 402 | 82 ms | $0.002 |
| 41 h ago | Amount "0.002" is not in atomic token units | 402 | 76 ms | $0.002 |
| 45 h ago | Amount "0.002" is not in atomic token units | 402 | 106 ms | $0.002 |
| 2 days ago | Amount "0.002" is not in atomic token units | 402 | 79 ms | $0.002 |
| 2 days ago | Amount "0.002" is not in atomic token units | 402 | 81 ms | $0.002 |
| 2 days ago | Amount "0.002" is not in atomic token units | 402 | 84 ms | $0.002 |
| 3 days ago | Amount "0.002" is not in atomic token units | 402 | 79 ms | $0.002 |