VirusTotal
8 / 90 engine detections
Open reportcrptmoy.com is a Crypto.com impersonation page detected by PhishDestroy on 2026-09-04. Risk: critical (100/100). Registrar: Realtime. Status: Content unavailable. Hosting: Cloudflare, Inc. PhishDestroy sent 1 abuse report. VirusTotal: 8/90 engines flag it. Google Safe Browsing flags it. Do not enter credentials or connect a wallet.
“Crypto.com”
8 / 90 engine detections
Open report1 threat-system alert
Open reportThreat flag recorded
Open reportMalicious
Open report6 community references
Open reportprovider verdict: clean
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | crptmoy.com |
malicious | Sinkholed |
PhishDestroy threat report
crptmoy.com is an impersonation phishing page that presented itself simply as "Crypto.com", the title shown in the browser tab. Its name is a compressed misspelling of the brand, aimed at Crypto.com customers who mistype the address or follow a link without reading it closely. PhishDestroy first flagged it on 2026-09-04. The site has been dead since 2026-09-11, and on 2026-10-19 its domain no longer resolved in DNS.
Lookalike exchange pages like this copy the branding and login flow of the real service so the visitor believes they are signing in to Crypto.com. Anything typed in goes to the operators: email, password, one-time 2FA codes and sometimes a wallet recovery phrase. With those, attackers log in to the genuine account in real time, change security settings and withdraw the balance. A captured recovery phrase gives them the wallet outright.
Eight of 90 VirusTotal engines flagged the domain on 2026-09-04: alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet, Google Safe Browsing, Gridinsoft, LevelBlue, Lionic and SOCRadar. That is a modest count, but it includes Google Safe Browsing, which listed the site under SOCIAL_ENGINEERING and drives warnings in Chrome and other major browsers. urlscan.io returned a malicious verdict and tagged the page as a crypto scam. The domain is also on the MetaMask and SEAL blocklists alongside PhishDestroy, and it appears in six AlienVault OTX threat pulses.
The domain was registered on 2026-07-30 through Realtime Register B.V. and sat for about five weeks before it surfaced as phishing, a gap that fits a domain bought ahead of a campaign. Traffic ran through Cloudflare, Inc. on an address geolocated to Canada. Cloudflare acts as a front, so this location reflects the proxy rather than the operators' own server.
If you entered your Crypto.com login on this site, open the official app right away. Change your password, reset 2FA, sign out all other sessions and review recent withdrawals and whitelisted addresses. Contact Crypto.com support about any activity you did not make. If you typed a recovery phrase, treat that wallet as compromised and move the funds to a new wallet created from a fresh phrase. If you connected a wallet, revoke any approvals granted around that time. Defenders should block the domain, search mail and proxy logs for earlier visits from their users, and watch for similarly compressed Crypto.com lookalikes.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a06d25-a9a2-7624-9126-b4bbe53ac001 |
|---|---|
| Final url | https://crptmoy.com/ |
| Status | 200 |
| Redirected | https-only |
| Redirects | [
{
"to": "https://crptmoy.com/",
"from": "http://crptmoy.com/",
"status": 307
}
] |
| Ip | 188.114.97.3 |
| Contacted domains | [
"esch20.oss-ap-southeast-1.aliyuncs.com",
"echang-bucket.oss-accelerate.aliyuncs.com"
] |
| Contacted IP addresses | [
"47.79.49.183",
"47.254.187.158",
"188.114.97.3"
] |
| Asns | [
"45102",
"13335"
] |
| Countries | [
"SG",
"DE"
] |
| Document hash | 129394071950b7f1044fe5cd73b20c40611ef59cdacd8c147a008e30f17608b7 |
| Script hashes | [
"bcee984fd52b4a82bd6b23543bb33f6472e076c125edbdd8756d29ca230628cb",
"ba302acc88913f80066015d4a5fadec2a4e8e48316b09c7cca1949138da35701",
"b18ac13a8d81ffbd5ed41226551cac5baa4c89922e2857009724e88099e22096",
"0741e2d7016a49351dee13f11c13e251e3cf7f9dc6bd6e3c8239fc2e8b65ec7b",
"711bcb3ed4a7b1490b4fb467f6b1553ad56d885e6020dc4e1a7f14d14742b87f",
"19b6064253aa9f5cf884171dac000919f3826dd71574f9fd9aee37fe5f1db2a6",
"89b58597a2ed145503723057e62be884247242c6216f8055e40bd3ad3063b39b",
"7cacc8b54c2056ad18df4a0d3ee2161e520b54fc1e017a0f34eb5e4d80b0198a",
"4abf2b61074bac344dfd0382faa443e7312f64db44cfdf12969cab179fe5b46d",
"f0be27efd14854cda28c2c6b1b46da6b23675919e4c81eeec884bc34e58bc27e"
] |
| Globals | [
"TradingView",
"addLink",
"addMeta",
"lib",
"rem",
"dpr",
"__VUE_INSTANCE_SETTERS__",
"__INTLIFY_PROD_DEVTOOLS__",
"__INTLIFY_JIT_COMPILATION__",
"__INTLIFY_DROP_MESSAGE_COMPILER__",
"__VUE_I18N_FULL_INSTALL__",
"__VUE_I18N_LEGACY_API__",
"setImmediate",
"clearImmediate",
"PubSub",
"__config",
"Buffer",
"__theme",
"__VUE__",
"__vite_is_modern_browser"
] |
| Storage keys | [
"Crypto.com_THEME",
"main",
"Crypto.com_LANGUAGE"
] |
| Tls | {
"san": [
"crptmoy.com",
"*.crptmoy.com"
],
"cipher": "AES_128_GCM",
"issuer": "WE1",
"subject": "crptmoy.com",
"protocol": "QUIC",
"valid_to": "2026-10-28T16:40:04Z",
"valid_from": "2026-07-30T15:42:28Z"
} |
| Domain age days | 35 |
| Apex age days | 35 |
| Tls age days | 36 |
| Tls valid days | 90 |
| Requests | 77 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 99,
"malicious": true
},
"overall": {
"tags": [
"phishing"
],
"score": 100,
"brands": [
"cryptoscam"
],
"malicious": true,
"categories": [
"phishing"
]
},
"urlscan": {
"tags": [
"phishing"
],
"score": 100,
"brands": [
"Crypto Scam"
],
"malicious": true,
"categories": [
"phishing"
]
}
} |
| HTTP headers | {
"server": "cloudflare",
"content-type": "text/html"
} |
Observed: · Retrieved:
| Uuid | f9bf0d99-df9f-410d-b91d-7870e9637250 |
|---|---|
| Final url | https://crptmoy.com/ |
| Status | 200 |
| History | [
{
"url": "https://crptmoy.com/",
"status": 200
}
] |
| DOM structure hash | 5b80b35bc5887aebef36a8cc4d26f12f5cea7b965ef900ec57de7b761908df5d |
| Document hash | 655d73a444a17cbe84effb766b5b7ad8282823e3c4f9fe913204e2b3adc622dd |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "crptmoy.com",
"type": "A",
"value": "104.21.41.49"
},
{
"name": "crptmoy.com",
"type": "A",
"value": "172.67.160.171"
},
{
"name": "crptmoy.com",
"type": "AAAA",
"value": "2606:4700:3031::ac43:a0ab"
},
{
"name": "crptmoy.com",
"type": "AAAA",
"value": "2606:4700:3037::6815:2931"
}
] |
| Dnssec valid | false |
| Ip | 104.21.41.49 |
| Registration record | {
"registrar": "Realtime Register B.V.",
"created": "2026-07-30T16:38:19Z",
"updated": "2026-07-30T16:39:20Z",
"expires": "2027-07-30T16:38:19Z",
"nameservers": [
"pat.ns.cloudflare.com",
"piers.ns.cloudflare.com"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 46,
"malicious": 11,
"suspicious": 1,
"undetected": 34
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"ESET": "suspicious",
"VIPRE": "phishing",
"G-Data": "phishing",
"Lionic": "phishing",
"Sophos": "malware",
"Fortinet": "phishing",
"SOCRadar": "phishing",
"BitDefender": "phishing",
"alphaMountain.ai": "phishing",
"Google Safe Browsing": "phishing",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Tags | [
"dga"
] |
| Categories | {
"alphaMountain.ai": "Phishing, Newly Registered (alphaMountain.ai)"
} |
| Registrar | Realtime Register B.V. |
| Created | 2026-07-30T16:38:19Z |
| Expires | 2027-07-30T16:38:19Z |
| Updated | 2026-09-28T16:38:42Z |
| First seen | 2026-07-30T17:42:22Z |
| DNS records | [
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700:3037::6815:2931"
},
{
"ttl": 300,
"type": "A",
"value": "172.67.160.171"
},
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700:3031::ac43:a0ab"
},
{
"ttl": 21600,
"type": "NS",
"value": "piers.ns.cloudflare.com"
},
{
"ttl": 300,
"type": "A",
"value": "104.21.41.49"
},
{
"ttl": 1800,
"type": "SOA",
"rname": "dns.cloudflare.com",
"value": "pat.ns.cloudflare.com"
},
{
"ttl": 21600,
"type": "NS",
"value": "pat.ns.cloudflare.com"
}
] |
| Dns at | 2026-09-01T00:02:56Z |
| Jarm | 27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c |
| Certificate | {
"san": [
"crptmoy.com",
"*.crptmoy.com"
],
"issuer": "Google Trust Services / WE1",
"serial": "16fa96234d5c90d713b6787c25f27514",
"sha256": "584f5616124b634a12e4860db2503a588c8cecf6a1ff5a1302e6ab70cbbf0300",
"subject": "crptmoy.com",
"valid_to": "2026-10-28T16:40:04Z",
"valid_from": "2026-07-30T15:42:28Z"
} |
| Registration record | {
"registrar": "Realtime Register B.V.",
"registrar_iana_id": "839",
"registrar_url": "http://www.realtimeregister.com",
"created": "2026-07-30T16:38:19Z",
"updated": "2026-09-28T16:38:42Z",
"expires": "2027-07-30T16:38:19Z",
"status": [
"clientHold"
],
"nameservers": [
"pat.ns.cloudflare.com",
"piers.ns.cloudflare.com"
],
"dnssec": "unsigned"
} |
| Registry data | {
"status": [
"active"
],
"events": {
"expiration": "2027-07-30T16:38:19Z",
"last changed": "2026-09-28T16:38:43Z",
"registration": "2026-07-30T16:38:19Z",
"registrar expiration": "2027-07-30T16:38:19Z",
"last update of RDAP database": "2026-10-12T11:02:44Z"
}
} |
No. PhishDestroy classifies crptmoy.com as a Crypto.com impersonation page (risk: critical, 100/100); it was first detected on 2026-09-04. VirusTotal: 8/90 engines flag it. Google Safe Browsing flags it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on crptmoy.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.
Last checked
Edge-IP reputation is not attributed to this domain.
pat.ns.cloudflare.compiers.ns.cloudflare.comLocation describes the IP network.
584f5616124b634a12e4860db2503a588c8cecf6a1ff5a1302e6ab70cbbf0300crptmoy.com*.crptmoy.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 crptmoy.com · checked Sep 4, 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→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
Unknown→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
Reachable→Unavailable
No flag recorded→Flag recorded
Reachable
Threat flag recorded
View source6 community references
View source8/90 engine detections
View sourcePD-20260904-72E79F
crptmoy.com
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
crptmoy.com
PD-20260904-72E79F Recipient: rtr-security-threats@realtimeregister.com 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 ↗
crptmoy.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.