VirusTotal
0 / 92 engine detections
Open report0 / 92 engine detections
Open reportScan report
Open reportno community references
Open reportScan report
Open reportNo threat flag
Open reportPage capture
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
AI-assisted evidence review
kakohub.monster surfaced on the PhishDestroy blocklist on 2026-10-19. The site is currently alive as of that date. It shows no obvious legitimate branding and is likely being used to lure cryptocurrency‑related traffic.
Typical sites of this type present a fake offer or service that encourages visitors to connect a crypto wallet or submit login credentials. Once a wallet is linked, the operator can request token approvals or initiate unauthorized transfers, resulting in loss of funds. Victims may also have their private keys or authentication data harvested for broader account takeover.
VirusTotal scanned the domain on 2026-10-19 and reported 0 detections out of 92 scanning engines, indicating no known malware signatures. The only independent flag comes from PhishDestroy, which placed the domain on its blocklist. No detections were reported by Google Safe Browsing, urlscan.io, or Spamhaus at the time of checking.
The domain was registered on 2026-10-13 through the registrar Spaceship, Inc., giving the operators a brief six‑day window before PhishDestroy identified it. Hosting is provided from the IP address 52.37.165.222, which is the sole network indicator available. No TLS certificate details are present in the current data.
Anyone who visited the site, entered credentials, or connected a wallet should immediately disconnect the wallet, revoke any token approvals granted to unknown contracts, change passwords, and enable two‑factor authentication on affected accounts. Monitor blockchain activity for unauthorized transfers and report any loss to the relevant exchange or wallet provider. Security teams should add kakohub.monster to internal blocklists, monitor DNS queries for the domain, and watch for traffic from the hosting IP address. Continue to follow threat‑intel feeds for any emerging indicators linked to this domain.
urlscan.io scan and screenshot: https://urlscan.io/result/01a153f9-a1ea-7313-b003-ef89fbc4f964/
VirusTotal report: https://www.virustotal.com/gui/domain/kakohub.monster
Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=kakohub.monster
Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/
Site owner? Request a review: https://phishdestroy.io/appeals/
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.
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.
launch1.spaceship.netlaunch2.spaceship.net0abb64346723544a41781896aaf91c70265c52eed6a980f33143fb9e7e976c18Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of kakohub.monster · checked Oct 19, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://kakohub.monster/https://kakohub.monster/Cache-Control: public, max-age=0, must-revalidateContent-Encoding: gzipContent-Type: text/html; charset=utf-8summary_large_imagepublic, max-age=0, must-revalidategzip1153text/html; charset=utf-8Mon, 19 Oct 2026 11:45:12 GMT"d68c277048e7db3d8864b9e8634ed638"Accept-EncodingValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Reachable
No threat flag
View source0/92 engine detections
View sourcekakohub.monster
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
kakohub.monster
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
kakohub.monster)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.