Vai al rapporto di sicurezza
Sicurezza del dominio e intelligence sulle minacce
kumibot.xyz favicon

kumibot.xyz

“KumiBot: Automated Polymarket Bot for 5-Minute Crypto Rounds”

Registrar
Spaceship
Resolved IP
162.252.199.183
Registered
02/10/2026
PhishDestroy assessment Critico
Disponibilità Contenuto non disponibile Il contenuto non era disponibile nell'ultima osservazione Osservato · HTTP probe
Corrispondenze della blocklist memorizzate: 2 Etichetta automatica del marchio: Across Dominio giovane: 18 giorni
OTX: 3 refs 14/10/2026 1 Report Sent
API
Questo dominio è stato segnalato come dannoso
Blocklist pubbliche che segnalano una corrispondenza: 2. Prestare estrema cautela: non inserire credenziali o informazioni personali.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
Riepilogo del rapporto

Imitazione di Across: kumibot.xyz — Contenuto non disponibile. Riepilogo delle prove: VirusTotal 0/92; 2 external blocklist matches (MetaMask, SEAL)…

L’analisi dettagliata di PhishDestroy AI resta in inglese per preservare il rapporto forense originale.

Source evidenceVirusTotal 0 / 92 · OTX 3 references 6 sources

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Critico
VirusTotal
0 / 92
OTX
3 community refs
Page captures
3

PhishDestroy threat report

Overview

kumibot.xyz presented itself as "KumiBot: Automated Polymarket Bot for 5-Minute Crypto Rounds", a pitch built to borrow Polymarket's name and appeal to traders chasing quick, hands-off profits on short crypto price rounds. PhishDestroy classifies it as an impersonation phishing page and first flagged it on 2026-10-14. The site went offline on 2026-10-16, and as of 2026-10-19 its domain no longer resolves.

How the scam works

Fake trading bots tied to a well-known platform follow a familiar pattern: the page promises automated wins on fast markets, then asks the visitor to connect a wallet, fund a bot balance or sign transactions to activate it. A deposit sent to such a service goes straight to the operators, and a signed approval can let them move tokens out of the wallet later. The "5-minute rounds" framing pushes victims to act quickly and to keep adding funds. Displayed profits or pending balances in these schemes are usually fabricated, and any request for a fee to withdraw them is a second round of theft.

Evidence

When it was checked on 2026-10-14, none of VirusTotal's 92 engines flagged the domain. That clean result reflects how new the site was, and it should not be read as a sign of safety. Wallet-focused defenders reached a different conclusion: MetaMask and the SEAL security alliance both list the domain alongside PhishDestroy. Three AlienVault OTX threat-intelligence pulses also reference it, showing that other researchers tracked it independently.

Infrastructure

The domain was registered through Spaceship, Inc. on 2026-10-02, only twelve days before PhishDestroy detected it. It was dead two days after detection, a short lifespan typical of throwaway phishing domains. It was hosted on the BL Networks (BLNWX) network, which is registered in the US, but the server's address geolocates to the Netherlands. A free Let's Encrypt certificate gave the page a browser padlock, which proves only that the connection was encrypted and says nothing about whether the site was legitimate.

What to do

If you connected a wallet to KumiBot, use a token-approval checker to revoke any permissions you granted, and move remaining assets to a fresh wallet if you signed anything you did not fully understand. If you sent funds to the "bot", do not pay any additional fee to unlock or withdraw a balance, because that money will also be lost. Report the transactions to your wallet provider and local authorities. Security teams should block the domain and watch for re-registrations or lookalike names that pair Polymarket with bot or auto-trading branding.

Extracted from stored page analysis

Observed indicators

10 wallet · 0 Telegram

Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.

ETH
0x06dc51826bc524d9a83770e7de9dd7e005b04524Format validated · Domain analysis
ETH
0x14767de7346a328d71f8fd4aed260d1cd67dec90Format validated · Domain analysis
ETH
0x27234d41eea8e8be1ce32facfc9adf389f318d2dFormat validated · Domain analysis
ETH
0x2f88bb53e3063f49a3e2776fdd10ea891a30dfd3Format validated · Domain analysis
ETH
0x7e5246abed17a5cff43a17b55b30f982f45200f5Format validated · Domain analysis
ETH
0xa19cbababc312f9df185e49d7004c249ed1ade6bFormat validated · Domain analysis
ETH
0xc6a2910714d2febe8730f8386277641f7c1fc9b7Format validated · Domain analysis
ETH
0xcc500cbcc8b7cf5bd21975ebbea34f21b5644c82Format validated · Domain analysis
ETH
0xdf4a97e9367cd823f000b4d686e9cb5dd563e8a3Format validated · Domain analysis
ETH
0xeee92f1cc6d6e0ad0b4ffda20b01cf3678e27ecbFormat validated · Domain analysis

IoC extraction recorded 2026-10-15 04:00:09 UTC

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Presente View source
PhishDestroy PhishDestroy list View source
SEAL Presente View source

Last checked

Acquisizione salvata · 3 captures

Observed page title
KumiBot: Automated Polymarket Bot for 5-Minute Crypto Rounds
Automated brand references
Across Ankr MetaMask Near Signal Ups
Certificato TLS
Emesso da Let's Encrypt / YE1 · stored validity ends in 74 days

Domain details

Dominio
URLScan verdict Analisi completata score 0 report ↗
Reputazione IP abuse score 0/100 0 reports checked 15/10/2026
OTX tags 2026-10all-domainsblocklistcryptodominidrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Spaceship US(US)
Contatto abusiabuse@spaceship.com
RegistrazioneCreato 02/10/2026 (18d · Very New!) — Expires 02/10/2027
Tempo fino alla prima indisponibilità 25h
Cosa conteggiamo Tempo trascorso dalla prima segnalazione di abuso archiviata alla prima osservazione che il contenuto non era disponibile. Ciò non ne stabilisce la causa.
Cosa contiene ogni rapporto I record archiviati dei report in uscita possono fare riferimento a prove disponibili in quel momento, come verdetti dei fornitori, dati di registrazione, dettagli di hosting, classificazioni o screenshot. Questa pagina non deduce l'esatto carico utile consegnato, la ricevuta, la conferma o l'azione da parte di un destinatario.
Dettagli tecniciProvenance & timestamps
Rilevato per la prima volta14/10/2026
DOM Analysisanalyzed 15/10/2026score 78/1006 brand signals
IoC Extractionscanned 15/10/202610 wallet · 0 Telegram IoCs
Submitted URLhttps://kumibot.xyz/
Favicon Hash
ID del caso
ICANN OVERSIGHT

Accreditamento e contesto RAA

Registrar accreditation and DNS abuse obligations

For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accountability draft Nulla viene inviato automaticamente.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
162.252.199.183
Network ASN
AS399629
Organization
BL Networks
Observed location
Amsterdam, NL
Server header
nginx

Nameserver 2

  • ns1.desec.io
  • ns2.desec.org

Location describes the IP network.

Certificato TLS

Issuer
Let's Encrypt / YE1
Valid from
2026-10-04 20:31:08
Valid until
2027-01-02 20:31:07
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-14 22:02:10 UTC
Collection source
PhishDestroy collector
Certificate fingerprint4615de41f6b722b31f3913bcfbbc67792755d9cb1a4087b449289e41d9ffe93d
Certificate names · 1 SANs
  • www.kumibot.xyz

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-20 08:34:10 UTC

Primary outcome DNS inattivo reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Sconosciuto Probe Inconclusive 20% 2026-10-19 01:18:42 UTC
RDAP registration Sconosciuto
Observed timeline last reachable: 2026-10-15 10:00:13 UTC last content: 2026-10-15 10:00:13 UTC current episode first observed: 2026-10-16 08:21:12 UTC observed RIP window: 2026-10-15 10:00:13 UTC → 2026-10-16 08:21:12 UTC · 22.35h midpoint estimate ≈ 2026-10-15 21:10:42 UTC · precision medium · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Riscontro delle informazioni sulle minacce · source references
ScamAdviser Public lookup
A public ScamAdviser lookup is available. Review its current score and warnings at the source; the existence of a lookup page is not itself a malicious verdict.
View on ScamAdviser
Live-fetched via CF worker proxy pool · cached 24h
Tecnologie · 5 identified
Detected via Cloudflare Radar · Wappalyzer engine
Segnala questo dominio Invia le prove e contribuisci a proteggere gli altri

Prove archiviate

Wayback Machine Snapshot
È disponibile un'istantanea storica per la revisione delle prove
View Archive
Analisi delle prestazioni del sito

Google PageSpeed Insights — mobile performance audit of kumibot.xyz · checked Oct 14, 2026

56
Needs Work
Performance
FCP
1.81s
First Contentful Paint
LCP
4.36s
Largest Contentful Paint
CLS
0.477
Cumulative Layout Shift
TBT
83ms
Total Blocking Time
SI
6.45s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: https://kumibot.xyz/
KumiBot: Automated Polymarket Bot for 5-Minute Crypto Rounds
KumiBot automates Polymarket's 5-minute crypto up/down rounds. It covers BTC, ETH, SOL, XRP, DOGE and BNB, taking a position every round strictly within the limits you set.
Risposta
HTTP 200
HTML body
175.3 KB
Compressed
51.2 KB
Links
33 internal · 2 external
Detected technologies
nginx
Selected response headers
Server: nginx
Content-Type: text/html; charset=UTF-8
X-Powered-By: Express
Cache-Control: public, max-age=0
Content-Encoding: gzip
Security headers present
Strict-Transport-SecurityContent-Security-PolicyX-Frame-OptionsX-Content-Type-OptionsReferrer-PolicyPermissions-Policy
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: 553bcd3798271564bddd03c3013a36812d1a675393839e1dea38bb986d5f505d
Open Graph title: KumiBot: Automated Polymarket Bot for 5-Minute Crypto Rounds
Open Graph description: KumiBot works Polymarket's 5 minute crypto rounds for you, taking an up or down position each round inside the limits you set.
Twitter card: summary
Saved response-header values · 16
Cache-Control
public, max-age=0
Connection
keep-alive
Content-Encoding
gzip
Content-Security-Policy
default-src 'self' https: data: blob:; script-src 'self' 'unsafe-inline' 'unsafe-eval' https:; style-src 'self' 'unsafe-inline' https:; img-src 'self' data: blob: https:; font-src 'self' data: https:; connect-src 'self' https: wss:; frame-ancestors 'self'
Content-Type
text/html; charset=UTF-8
Date
Wed, 14 Oct 2026 21:00:15 GMT
Etag
W/"2bd33-1a13c349d38"
Last-Modified
Wed, 14 Oct 2026 20:57:23 GMT
Permissions-Policy
camera=(), microphone=(), geolocation=(), payment=()
Referrer-Policy
strict-origin-when-cross-origin
Server
nginx
Strict-Transport-Security
max-age=31536000; includeSubDomains
Transfer-Encoding
chunked
X-Content-Type-Options
nosniff
X-Frame-Options
SAMEORIGIN
X-Powered-By
Express

Values retained by the collector; long values may be shortened during collection.

Registration & observation details9

Availability observations

Last reachable observation
Last content observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
22.35
Estimate basis
Bounded by observations
Estimate precision
Medio

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

kumibot.xyz
Risultato salvato
Cloaked / Filtered
Stored observation history6

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Sconosciuto→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Sconosciuto→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Sconosciuto→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Raggiungibile→Non disponibile

  5. Availability monitor · Recorded state

    Sconosciuto→live_content

    content_served

Earlier observations 1
  1. Availability monitor · First collection record

    Raggiungibile

Recorded activity

6 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    0/92 engine detections

    View source
  3. AlienVault OTX

    3 community references

    View source
  4. Abuse report sent

    PD-20261014-AEDC3F

    abuse@spaceship.com
  5. URLScan

    Page captured

    View source
  6. Added to PhishDestroy

    kumibot.xyz

    View source

Domini simili

79 domini simili memorizzati

Mostra tutto (67)
metasmask.io insertion Report interno metramask.io insertion Report interno mewtamask.io insertion Report interno mmetamask.io homoglyph Report interno mtamask.io omission Report interno mwetamask.io insertion Report interno nmetamask.io homoglyph Report interno metamark.io bitsquatting Report interno metamaskj.io addition Report interno metammask.io homoglyph Report interno metamnask.io homoglyph Report interno emtamask.io transposition m-etamask.io hyphenation meamask.io omission meatmask.io transposition meramask.io replacement mertamask.io insertion metaamask.io repetition metaamsk.io transposition metaask.io omission metalmask.io insertion metamaask.io insertion metamadsk.io insertion metamaek.io replacement metamak.io omission metamas.io omission metamasak.io insertion metamasdk.io insertion metamask-io.com various metamasl.io replacement metamasm.io replacement metamsak.io transposition metamsk.io omission metamusk.io vowel-swap metamzsk.io replacement metarnask.io homoglyph metmaask.io transposition metmask.io omission metsamask.io insertion metsmask.io replacement mettamask.io repetition metwmask.io replacement metyamask.io insertion metzmask.io replacement meyamask.io replacement meytamask.io insertion mitamask.io vowel-swap mnetamask.io homoglyph mretamask.io insertion mrtamask.io replacement mstamask.io replacement mteamask.io transposition mwtamask.io replacement rnetamask.io homoglyph matamask.io bitsquatting mdtamask.io bitsquatting metamasi.io bitsquatting metamasj.io bitsquatting metamaska.io addition metamaskk.io addition metamaskl.io addition metamaso.io bitsquatting metamesk.io bitsquatting metamqsk.io bitsquatting metemask.io bitsquatting netamask.io homoglyph xn--metamas-bhb.io homoglyph

Intelligence della comunità

1 segnalazione della comunità

CategoriaPHISHING

Kumibot.xyz is a phishing scam intended to scam Polymarket users.

Dati e relazioni esterne

Community Scam Report — ChainAbuse
1 report filed for kumibot.xyz (1 written by a person) · category: Phishing · source checked
“Kumibot.xyz is a phishing scam intended to scam Polymarket users.”
— reported by Anonymous on Oct 6, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
Istantanea delle prove inviate
Sent: Ledger records: 1 Case ID: PD-20261014-AEDC3F Recipient: abuse@spaceship.com
PDF notice generated
Analisi approfondita
Help & reporting

Questo sito ti ha influenzato in qualche modo?

5 evidence signal groups linked 1 stored notification records Contenuto non disponibile
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Se hai inserito credenziali dell'account, informazioni personali o di pagamento oppure hai scaricato un file da questo dominio, agisci immediatamente. Di seguito sono riportate le risorse per aiutarti a segnalare l'incidente e proteggerti.

Official reporting routes

Europol
Trova il canale di segnalazione ufficiale per il tuo paese dell'UE
National police directory
Find your country
Attenzione ai truffatori che promettono il recupero dei fondi! I criminali possono contattare nuovamente le vittime fingendo di essere investigatori, avvocati o agenti di recupero. Non pagare commissioni anticipate né condividere credenziali. Scopri di più sulle frodi relative ai sussidi di recupero →

Segnalalo alle autorità locali

Seleziona il tuo Paese per ottenere contatti ufficiali del crimine informatico o creare una bozza di reclamo →.

Elenco di 97 paesi

Template-based draft · optional AI wording assistance requires separate consent

Bozza assistita dall'intelligenza artificiale: i dettagli dell'incidente vengono elaborati dal fornitore di intelligenza artificiale · Controllalo e invialo tu stesso
After a phishing incident

Raccomandazioni e consigli per le vittime

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

Cosa devo fare subito?

Urgente

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Modifica tutte le password — e-mail, account Exchange, qualsiasi servizio che utilizzi la stessa password
  • Abilita l'autenticazione a due fattori (2FA) utilizzando un'app di autenticazione (non via SMS). Disattiva il recupero tramite SMS
  • Carte congelate se hai inserito i tuoi dati bancari sul sito di phishing

Quali informazioni devo raccogliere per la mia relazione?

Linee guida dell'FBI

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Date e orari esatti — di ogni transazione e del primo contatto con il truffatore
  • Schermate — siti web truffaldini, messaggi in chat, e-mail, transazioni tramite portafoglio digitale, social media
  • Tutti gli URL e i domini utilizzato dal truffatore (tra cui kumibot.xyz)
  • Comunicazioni — e-mail, SMS, numeri di telefono, nomi utente utilizzati dal truffatore

Anche se non conosci tutti i dettagli — sporgere comunque denuncia. Anche le informazioni parziali sono comunque utili alle indagini.

A chi devo segnalare la truffa?

  • FBI IC3 — Internet Crime Complaint Center (sistema di segnalazione federale degli Stati Uniti)
  • Europol — Segnalazioni relative alla criminalità informatica in Europa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Polizia locale — crea un documento ufficiale, anche se non è in grado di agire immediatamente

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Siti web fasulli — cloni perfetti, al pixel, di siti legittimi con domini leggermente modificati
  • Macellazione dei suini — fiducia conquistata nel corso di settimane tramite Telegram/WhatsApp/app di incontri, per poi rubare i soldi
  • Truffe legate al recupero dei fondi — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Truffe basate sull'intelligenza artificiale — i deepfake, il phishing automatizzato e i siti generati dall’intelligenza artificiale rendono più difficile individuare le frodi

Come posso proteggermi in futuro?

  • Aggiungi i siti ufficiali ai preferiti — Non cliccare mai sui link contenuti nelle e-mail, nei messaggi diretti o negli annunci pubblicitari
  • Verifica i domini — controllare PhishDestroy prima di interagire. Verifica l'HTTPS, l'ortografia e l'età del dominio
  • "Troppo bello per essere vero" = truffa — rendimenti garantiti, testimonial di personaggi famosi, scadenze urgenti

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Rimani informato, rimani al sicuro

Controlla le minacce in tempo reale oppure contesta questa segnalazione se ritieni che si tratti di un falso positivo

Feed in tempo reale sulle minacce Contesta questo annuncio
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Incorpora questo rapporto

Condividi queste informazioni sulle minacce sul tuo sito web o sul tuo blog

embed.html
<iframe
  src="https://phishdestroy.io/it/embed/domain/kumibot.xyz"
  title="PhishDestroy threat report for kumibot.xyz"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>