PhishDestroy has added botsea.club to its internal blocklist as a suspicious domain. The domain was first observed by PhishDestroy on 2026-10-20. No page title was recorded at the time of observation.
How the scam works
Because the domain is flagged without a concrete scheme classification, the exact malicious intent cannot be determined. The presence of multiple vendor detections suggests it may be used for phishing, fraud, or other illicit activities, but no specific behavior was observed.
Evidence
VirusTotal scanned the domain on 2026-10-20 and reported 8 detections from 92 engines, including alphaMountain.ai, BitDefender, CRDF, DNS8, Fortinet, G-Data, Gridinsoft and SOCRadar. Google Safe Browsing checked the same day and did not flag the site. External blocklists OpenPhish and Phishunt listed botsea.club as malicious on 2026-10-20. PhishDestroy’s internal list also marked the domain as suspicious on that date. OTX had no pulses referencing the domain as of 2026-10-20.
Infrastructure
The domain was registered on 2026-09-01 through Dominet (HK) Limited, 49 days before PhishDestroy’s first observation. The recorded IP address associated with the site is 50.6.202.214.
What to do
If you visited botsea.club, ensure no credentials or personal data were entered and change passwords for any accounts that may have been used. Do not approve any wallet or financial permissions linked to the site. Network defenders should add the domain and its recorded IP address to blocklists and review access logs for any connections on 2026-10-20. Continue monitoring reputable threat feeds for any future updates on this domain.
DOM Analysisanalyzed 2026年10月20日score 25/1003 brand signals
Submitted URLhttp://botsea.club/76etfl/g5eg
ケース ID
ICANN OVERSIGHT
認定と 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.
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.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
(US)
