VirusTotal
10 / 91 engine detections
보고서 열기“Ruqvexa”
ruqvexa.app — 마지막으로 알려진 활성 (HTTP 200). 브랜드 사칭: MetaMask; 사기 유형: Impersonation. 증거 요약: VirusTotal 10/91 (alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet); 2 external blocklist matches (MetaMask, SEAL); CF Radar malicious; PhishDestroy score 95/100. 등록기관: CloudFlare.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
10 / 91 engine detections
보고서 열기악성
보고서 열기no community references
보고서 열기No threat flag
보고서 열기No malicious flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
ruqvexa.app is an impersonation phishing page that presents itself under the name "Ruqvexa". MetaMask and SEAL both list it, which places it among threats to crypto wallet users. PhishDestroy first detected it on 2026-09-29. As of 2026-10-19 the site was still online and serving its phishing content.
Impersonation sites like this copy the look and language of a legitimate crypto service so visitors trust them enough to act. The page carries only its own invented name, "Ruqvexa", rather than a recognizable brand. Its purpose matches our impersonation classification: it gets visitors to hand over something valuable. On sites in this category, that usually means connecting a wallet and signing a transaction or token approval, typing in a recovery phrase, or entering login details. Any of these can give the operators control of the victim's funds or accounts.
On 2026-10-01, 10 of 91 VirusTotal engines flagged the domain. Those vendors were alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft and Kaspersky. That is a minority of engines, but several of them are mainstream security products, so many users are already warned. Wallet-side protection matters most here. MetaMask's blocklist and SEAL both include the domain alongside PhishDestroy, so MetaMask users should see a warning before the page loads.
The domain was registered on 2026-08-25 through CloudFlare, Inc. That is roughly five weeks before PhishDestroy flagged it, a short gap typical of disposable scam domains. Traffic passes through Cloudflare's network, with the address geolocated to Canada, so the real origin server is hidden behind the proxy. The certificate from Google Trust Services is a free, automatically issued one. The padlock in the browser therefore says nothing about whether the site is legitimate.
If you connected a wallet to ruqvexa.app, review and revoke any token approvals or permissions granted during that visit using a trusted approval-management tool. Move remaining assets if you signed anything you did not fully understand. If you typed in a recovery phrase, treat that wallet as compromised and transfer funds to a new wallet with a fresh phrase right away. If you entered a password, change it wherever you reused it and turn on two-factor authentication. Security teams should block the domain at DNS and proxy level and check logs for users who reached it.
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.
Edge-IP 평판은 이 도메인에 귀속되지 않습니다.
betty.ns.cloudflare.comrazvan.ns.cloudflare.comLocation describes the IP network.
2dcf5f496c80a602b1305468e700387e3d70d0e1f260b63a7f10e640d3076ee9Saved 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.ruqvexa.appDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of ruqvexa.app · 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.
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
No threat flag
View source10/91 engine detections
View sourcePage captured
View sourceruqvexa.app
View source저장된 유사 도메인 79개
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
ruqvexa.app
Listed domains receive at least one abuse report; this entry has no retained notification history.
계정 자격 증명, 개인 정보 또는 결제 정보를 입력했거나 이 도메인에서 파일을 다운로드한 경우 즉시 조치를 취하세요. 다음은 사건을 신고하고 자신을 보호하는 데 도움이 되는 리소스입니다.
공식 사이버 범죄 연락처 또는 불만사항 초안 작성 →를 받으려면 국가를 선택하세요.
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 ↗
ruqvexa.app)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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
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.