VirusTotal
18 / 92 engine detections
Open reportblockwavewallets.com is a phishing page detected by PhishDestroy on 2026-09-29. Risk: critical (100/100). Registrar: Megazone. Status: Last known active. Hosting: Cloudflare, Inc. PhishDestroy sent 1 abuse report. VirusTotal: 18/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.
“Block wave - 로그인”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@hosting.kr.
The latest stored availability evidence still shows the domain reachable; 23 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
18 / 92 engine detections
Open report2 det.
Open reportSuspicious
Open reportDBL_PHISH
5 community references
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
blockwavewallets.com poses as the sign-in page of a crypto wallet service called Block Wave. Its page title, "Block wave - 로그인", uses the Korean word for "login", which points to Korean-speaking wallet users as the intended audience. PhishDestroy first flagged the domain on 2026-09-29. As of 2026-10-19 the site was still online and serving its phishing content.
This is a lookalike login screen. The domain combines the brand name with the generic word "wallets" to look like an official address. Anyone who signs in hands their username, password and any one-time codes to the operators. Wallet impersonation pages often go further and ask for a recovery phrase or private key to "restore" or "verify" access. With a recovery phrase, an attacker can rebuild the wallet on their own device and empty it, and blockchain transfers cannot be reversed.
On 2026-10-07, 18 of 92 VirusTotal engines flagged the domain. They included BitDefender, ESET, Fortinet, G-Data, Forcepoint ThreatSeeker, alphaMountain.ai, CRDF and Criminal IP. Spamhaus lists the domain in its DBL under the phishing category, so many mail filters will block messages that link to it. The domain also appears in five AlienVault OTX threat pulses. PhishDestroy carries it on its own blocklist.
The domain was registered on 2026-09-10 through Megazone Corp. (HOSTING.KR), a Korean registrar, which matches the Korean-language login page. PhishDestroy detected it 19 days after registration, a typical gap for a phishing domain set up shortly before a campaign. The site sits behind Cloudflare, with the edge address geolocated to Canada, so its real origin server is hidden. It uses a free Let's Encrypt certificate, so the padlock in the browser says nothing about whether the site is legitimate.
If you entered a password on this page, change it right away on the genuine Block Wave service and anywhere else you reused it. Then reset two-factor authentication and review recent logins. If you typed a recovery phrase or private key, treat the wallet as compromised and move any remaining funds to a newly created wallet immediately. If you connected a wallet and signed anything, revoke token approvals with a reputable approval checker. Defenders should block the domain at DNS, proxy and mail gateways and search their logs for earlier visits. Abuse reports to Cloudflare and the registrar can help get the site taken down.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a0eb6f-1c12-71ef-946f-6b3f6965dd42 |
|---|---|
| Final url | https://blockwavewallets.com/admin/login |
| Status | 200 |
| Redirected | https-only |
| Redirects | [
{
"to": "https://blockwavewallets.com/admin/login",
"from": "http://blockwavewallets.com/admin/login",
"status": 307
}
] |
| Ip | 104.21.81.35 |
| Contacted IP addresses | [
"104.21.81.35"
] |
| Asns | [
"13335"
] |
| Document hash | e1cf6d9f8aef0a7e9219e155e76a938adc28d16af997fc919b757905f915d23d |
| Globals | [
"requestResize"
] |
| Tls | {
"san": [
"*.blockwavewallets.com",
"blockwavewallets.com"
],
"cipher": "AES_128_GCM",
"issuer": "YE2",
"subject": "blockwavewallets.com",
"protocol": "QUIC",
"valid_to": "2026-12-09T07:27:20Z",
"valid_from": "2026-09-10T07:27:21Z"
} |
| Domain age days | 18 |
| Apex age days | 18 |
| Tls age days | 18 |
| Tls valid days | 89 |
| Requests | 3 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 90,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "cloudflare",
"content-type": "text/html; charset=utf-8"
} |
Observed: · Retrieved:
| Uuid | 67a31288-6d25-4492-9820-7ecf0f9fe37d |
|---|---|
| Final url | https://blockwavewallets.com/ |
| Status | 200 |
| History | [
{
"url": "https://blockwavewallets.com/",
"status": 200
}
] |
| DOM structure hash | c7308ae3da4d903dd3087945284e6275d14897bab9488d0a60ed7e9798e8024e |
| Document hash | 912dd241f38c8e0b6dc8a9735f9d17731c8cbe13ea2313661e42a5238f46e71f |
| Phishing v2 | [
"phishing"
] |
| Domain risks | [
"Newly Seen Domains",
"Security Risks",
"New Domains"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "blockwavewallets.com",
"type": "A",
"value": "104.21.81.35"
},
{
"name": "blockwavewallets.com",
"type": "A",
"value": "172.67.137.211"
},
{
"name": "blockwavewallets.com",
"type": "AAAA",
"value": "2606:4700:3030::ac43:89d3"
},
{
"name": "blockwavewallets.com",
"type": "AAAA",
"value": "2606:4700:3032::6815:5123"
}
] |
| Dnssec valid | false |
| Ip | 104.21.81.35 |
| Registration record | {
"registrar": "Megazone Corp., dba HOSTING.KR",
"created": "2026-09-10T08:12:03Z",
"updated": "2026-09-10T08:17:59Z",
"expires": "2027-09-10T08:12:03Z",
"nameservers": [
"kareem.ns.cloudflare.com",
"wanda.ns.cloudflare.com"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 44,
"malicious": 17,
"suspicious": 2,
"undetected": 29
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"ESET": "suspicious",
"VIPRE": "phishing",
"G-Data": "phishing",
"Lionic": "phishing",
"Sophos": "malware",
"CyRadar": "phishing",
"Webroot": "malicious",
"Fortinet": "spam",
"SOCRadar": "phishing",
"URLQuery": "malicious",
"Kaspersky": "phishing",
"LevelBlue": "phishing",
"Gridinsoft": "phishing",
"MalwareURL": "phishing",
"BitDefender": "phishing",
"Criminal IP": "phishing",
"alphaMountain.ai": "phishing",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Created | 2026-09-10T00:00:00Z |
| First seen | 2026-09-10T08:29:09Z |
| DNS records | [
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700:3032::6815:5123"
},
{
"ttl": 300,
"type": "A",
"value": "104.21.81.35"
},
{
"ttl": 21600,
"type": "NS",
"value": "kareem.ns.cloudflare.com"
},
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700:3030::ac43:89d3"
},
{
"ttl": 21600,
"type": "NS",
"value": "wanda.ns.cloudflare.com"
},
{
"ttl": 1800,
"type": "SOA",
"rname": "dns.cloudflare.com",
"value": "kareem.ns.cloudflare.com"
},
{
"ttl": 300,
"type": "A",
"value": "172.67.137.211"
}
] |
| Dns at | 2026-10-18T16:34:25Z |
| Jarm | 27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c |
| Certificate | {
"san": [
"*.blockwavewallets.com",
"blockwavewallets.com"
],
"issuer": "Let's Encrypt / YE2",
"serial": "5f1bb61e4a6f36643aa514812fbea8b8f5d",
"sha256": "37b25b27cff5dae788563b5ba5d71bae146574c6090f32a699b5dce3c66c35bc",
"subject": "blockwavewallets.com",
"valid_to": "2026-12-09T07:27:20Z",
"valid_from": "2026-09-10T07:27:21Z"
} |
| Registry data | {
"status": [
"client transfer prohibited"
],
"events": {
"expiration": "2027-09-10T08:12:03Z",
"last changed": "2026-09-10T08:17:59Z",
"registration": "2026-09-10T08:12:03Z",
"last update of RDAP database": "2026-10-17T07:40:56Z"
},
"registrar": "Megazone Corp., dba HOSTING.KR",
"registrar_iana_id": "1489"
} |
No. PhishDestroy classifies blockwavewallets.com as a phishing page (risk: critical, 100/100); it was first detected on 2026-09-29. VirusTotal: 18/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on blockwavewallets.com. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
Edge-IP reputation is not attributed to this domain.
kareem.ns.cloudflare.comwanda.ns.cloudflare.comLocation describes the IP network.
37b25b27cff5dae788563b5ba5d71bae146574c6090f32a699b5dce3c66c35bc*.blockwavewallets.comblockwavewallets.comSaved 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 blockwavewallets.com · checked Sep 29, 2026
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.
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
redirected→live_content
content_served
Unknown→redirected
http_redirect
live_content→redirected
http_redirect
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
live_content
content_served
11→12
Reachable
No threat flag
View source18/92 engine detections
View source5 community references
View sourcePD-20260929-4D2424
blockwavewallets.com
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
blockwavewallets.com
PD-20260929-4D2424 Recipient: abuse@hosting.kr 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 ↗
blockwavewallets.com)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.