VirusTotal
15 / 92 engine detections
Open reportsverchvpn.space is a Telegram impersonation page detected by PhishDestroy on 2026-10-12. Risk: critical (100/100). Registrar: Registrar of Domain Na…. Status: Last known active. Hosting: GIR-AS GLOBAL INTERNET SOLUTIONS LLC, RU. VirusTotal: 15/92 engines flag it. Do not enter credentials or connect a wallet.
“MYXA VPN — Premium бесплатно”
15 / 92 engine detections
Open reportMalicious
Open report8 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
sverchvpn.space presents itself as MYXA VPN under the Russian-language headline "Premium бесплатно" ("Premium for free"). It is built to catch Russian-speaking users hunting for a no-cost premium VPN. PhishDestroy first saw it on 2026-10-13, and it was still online serving live content on 2026-10-19.
The page uses MYXA VPN's name and a free Premium promise to win trust from people who want a VPN without paying. Impersonation pages of this kind usually push visitors to download a supposed client, sign in with an existing account, or enter payment details to "activate" the free tier. Whatever the visitor provides goes to the operators instead of the real service. That can mean stolen logins, stolen card data, or an unwanted program on the device.
On 2026-10-16, 15 of 92 VirusTotal engines flagged the domain. The vendors included Kaspersky, Fortinet, Forcepoint ThreatSeeker, ESTsecurity, Gridinsoft, CyRadar, CRDF and alphaMountain.ai. Because these are separate vendors with their own detection pipelines, the agreement is meaningful even though most engines have not yet caught up. The domain is listed on the PhishDestroy and CryptoFirewall blocklists, and it appears in 8 AlienVault OTX threat pulses, so other researchers are tracking it too.
The domain was registered through REG.RU on 2026-04-05, about six months before PhishDestroy detected it. That gap suggests it was set up well in advance rather than spun up for a quick strike. It is hosted in Russia on GIR-AS Global Internet Solutions LLC. That matches the Russian-language lure and points to a locally focused operation.
Do not download anything from this site or type any credentials into it. If you installed a "MYXA VPN" client from here, uninstall it and run a full scan with a reputable antivirus. If you entered a password, change it everywhere you reused it and turn on two-factor authentication. If you submitted card details, contact your bank to block the card and dispute any unfamiliar charges. Security teams should block the domain and its hosting address at DNS and proxy level, and check logs for users who visited it.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a01a01-d1e7-723a-b4b6-e79c6ad376a6 |
|---|---|
| Final url | https://sverchvpn.space/ |
| Status | 200 |
| Redirected | off-domain |
| Redirects | [
{
"to": "https://murvpn.space/",
"from": "http://murvpn.space/",
"status": 307
},
{
"to": "https://sverchvpn.space/",
"from": "https://murvpn.space/",
"status": 301
}
] |
| Ip | 212.192.14.75 |
| Ptr | 23052.ip-ptr.tech |
| Contacted domains | [
"mc.yandex.com",
"mc.yandex.ru",
"murvpn.space"
] |
| Contacted IP addresses | [
"2a02:6b8::1:119",
"212.192.14.75"
] |
| Asns | [
"13238",
"207713"
] |
| Countries | [
"RU"
] |
| Linked domains | [
"telegram.me",
"app.myxavpn.pro"
] |
| Social | [
"https://telegram.me/myxavpn_bot"
] |
| Document hash | 9128e92b35d5c823fc8c8322b221a96f5ff4214ab2578efff3e415bae6f140d4 |
| Globals | [
"ym",
"Ya",
"yaCounter109410454",
"dataLayer"
] |
| Cookies | [
"bh",
"_ym_uid",
"_ym_d",
"_ym_isad",
"sync_cookie_csrf",
"yabs-sid",
"i",
"yandexuid",
"yuidss",
"ymex",
"receive-cookie-deprecation",
"sync_cookie_csrf_secondary",
"sync_cookie_ok_secondary",
"_ym_visorc"
] |
| Storage keys | [
"_ymBRC",
"_ym_synced",
"_ym109410454_lsid",
"_ym109410454:0_reqNum",
"_ym_uid",
"_ym_retryReqs",
"_ym_wv2rf:109410454:0",
"__ym_tab_guid"
] |
| Tls | {
"san": [
"sverchvpn.space",
"www.sverchvpn.space"
],
"cipher": "AES_128_GCM",
"issuer": "YE2",
"subject": "sverchvpn.space",
"protocol": "TLS 1.3",
"valid_to": "2026-11-05T12:04:25Z",
"valid_from": "2026-08-07T12:04:26Z"
} |
| Domain age days | 135 |
| Apex age days | 135 |
| Tls age days | 12 |
| Tls valid days | 89 |
| Requests | 8 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 99,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "nginx/1.24.0 (Ubuntu)",
"content-type": "text/html"
} |
Observed: · Retrieved:
| Uuid | 6c28886f-f1c9-4b0d-873a-9534b2eb0fa0 |
|---|---|
| Final url | https://sverchvpn.space/ |
| Status | 200 |
| History | [
{
"url": "https://sverchvpn.space/",
"status": 200
}
] |
| DOM structure hash | e17e4149cdf5b95266930a761788ea97a137cade92f0952c9669913f082feace |
| Document hash | 9128e92b35d5c823fc8c8322b221a96f5ff4214ab2578efff3e415bae6f140d4 |
| Phishing v2 | [
"phishing"
] |
| Domain risks | [
"Malware",
"Security threats",
"CIPA Filter",
"CIPA"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "sverchvpn.space",
"type": "A",
"value": "212.192.14.75"
}
] |
| Dnssec valid | false |
| Ip | 212.192.14.75 |
| Verdict | {
"tags": [
"malware"
],
"malicious": true,
"categories": [
"malware"
]
} |
| Registration record | {
"registrar": "Registrar of Domain Names REG.RU LLC",
"created": "2026-04-05T12:43:41Z",
"updated": "2026-04-10T12:44:12Z",
"expires": "2027-04-05T12:43:41Z",
"nameservers": [
"ns1.reg.ru",
"ns2.reg.ru"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 45,
"malicious": 14,
"suspicious": 1,
"undetected": 32
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"Lionic": "malicious",
"Sophos": "malware",
"CyRadar": "malicious",
"Webroot": "malicious",
"Fortinet": "malware",
"SOCRadar": "phishing",
"URLQuery": "malicious",
"Kaspersky": "malware",
"LevelBlue": "phishing",
"Seclookup": "malicious",
"Gridinsoft": "suspicious",
"ESTsecurity": "malicious",
"alphaMountain.ai": "malicious",
"Forcepoint ThreatSeeker": "malicious"
} |
| Reputation | 0 |
| Created | 2026-04-05T00:00:00Z |
| Updated | 2026-04-10T00:00:00Z |
| First seen | 2026-04-05T13:10:54Z |
| DNS records | [
{
"ttl": 21600,
"type": "NS",
"value": "ns2.reg.ru"
},
{
"ttl": 21600,
"type": "SOA",
"rname": "hostmaster.ns1.reg.ru",
"value": "ns1.reg.ru"
},
{
"ttl": 21600,
"type": "NS",
"value": "ns1.reg.ru"
},
{
"ttl": 19406,
"type": "A",
"value": "212.192.14.75"
}
] |
| Dns at | 2026-10-20T00:11:19Z |
| Jarm | 27d40d40d00040d00042d43d0000007d20e9b9a3e87aa1ec17cb4d646ce9a5 |
| Certificate | {
"san": [
"sverchvpn.space",
"www.sverchvpn.space"
],
"issuer": "Let's Encrypt / YE2",
"serial": "58d3f36452f2b6aaf34f766a449a5edcf4d",
"sha256": "c458be1c4f9b1251af989314419c03ff5f46925ea15b848675c110e805ae23a1",
"subject": "sverchvpn.space",
"valid_to": "2027-01-04T17:44:57Z",
"valid_from": "2026-10-06T17:44:58Z"
} |
| Registry data | {
"status": [
"client transfer prohibited"
],
"events": {
"expiration": "2027-04-05T12:43:42Z",
"registration": "2026-04-05T12:43:42Z",
"registrar expiration": "2027-04-05T12:43:42Z",
"last update of RDAP database": "2026-10-13T23:24:46Z"
},
"registrar": "Registrar of Domain Names REG.RU LLC",
"registrar_iana_id": "1606"
} |
No. PhishDestroy classifies sverchvpn.space as a Telegram impersonation page (risk: critical, 100/100); it was first detected on 2026-10-12. VirusTotal: 15/92 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on sverchvpn.space. 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
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.
ns2.reg.ruLocation describes the IP network.
c458be1c4f9b1251af989314419c03ff5f46925ea15b848675c110e805ae23a1www.sverchvpn.spaceSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.sverchvpn.spaceDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of sverchvpn.space · checked Oct 13, 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
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
No threat flag
View source15/92 engine detections
View source8 community references
View sourcesverchvpn.space
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
sverchvpn.space
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 ↗
sverchvpn.space)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.