VirusTotal
7 / 92 engine detections
レポートを開く“Ruqvexa”
Aaveなりすまし: ruqvexabit.com — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 7/92 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, Kaspersky); 2…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
7 / 92 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
ruqvexabit.com is an impersonation phishing page that presents itself under the name "Ruqvexa" and is aimed at cryptocurrency users. PhishDestroy first flagged it on 2026-10-14, only two days after the domain was registered. As of 2026-10-19 the site was still online and serving its content, so it remains an active danger to anyone who lands on it.
Impersonation sites like this borrow a trading or wallet brand's name and look so visitors believe they are on a real crypto service. The "Ruqvexa" page invites users to sign in, connect a wallet or fund an account. Whatever is typed or approved goes to the operators. That can mean stolen login credentials, a recovery phrase that hands over full wallet control, or deposits that are never returned. Because the domain adds "bit" to the brand name, it can pass at a glance for an official exchange address.
On 2026-10-18, seven of 92 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, Kaspersky, SOCRadar and VIPRE. That count is modest, so many security tools may still let the site load without a warning. The crypto ecosystem's own defenses carry more weight here. Besides PhishDestroy, the domain appears on the MetaMask and SEAL blocklists, both of which track threats to wallet users.
The domain was registered through Cloudflare, Inc. on 2026-10-12 and was caught within 48 hours, a fast turnaround typical of short-lived scam domains. Its traffic runs through Cloudflare's network, with a Canadian address, which puts the site behind a proxy and hides the real origin server. The Let's Encrypt certificate gives the page a padlock, but that only means the connection is encrypted. It says nothing about whether the site is legitimate.
If you entered a password on this site, change it wherever you reuse it and turn on app-based two-factor authentication. If you typed in a seed phrase, treat that wallet as compromised and move any remaining funds to a new wallet right away. Anyone who connected a wallet and signed transactions should review and revoke token approvals they don't recognise. Do not send any further "fees" to unlock deposited funds. Security teams should block the domain at the DNS and proxy level and report it to the registrar and the hosting network.
Last checked
Edge-IP の評判はこのドメインに起因しません。
betty.ns.cloudflare.comrazvan.ns.cloudflare.comLocation describes the IP network.
d4f7c140a1679751145d3fc1f6295f3cb1c250b1494b40801c181a292e493938Saved 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.
down.ruqvexabit.comDomain recordwww.ruqvexabit.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of ruqvexabit.com · checked Oct 14, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://ruqvexabit.com/https://ruqvexabit.com/Content-Type: text/htmlServer: cloudflareCF-Cache-Status: DYNAMICContent-Encoding: gziph3=":443"; ma=86400DYNAMICa4a917f219d99f1b-FRAkeep-alivegziptext/htmlWed, 14 Oct 2026 19:47:02 GMT{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=3BP5gnsMp9t%2B4U38eVVeW8DRiDK6nn%2FRw5XZrmXCr3zh4fA0PBImlu5yxK%2Bv9tDTe4M4XUH2r%2FuCbH448HW1KQF7F54xmrQjQURpuLIy8AH9WXV1eURxw%2BWa6jpIMuNi8Q%3Dcloudflaremax-age=31536000chunkedAccept-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.
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
到達可能
No threat flag
View source7/92 engine detections
View sourcePage captured
View sourceruqvexabit.com
View source保存された類似ドメイン:95 件
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
ruqvexabit.com
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 ↗
ruqvexabit.com)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.