VirusTotal
6 / 91 engine detections
レポートを開く“DApp”
フィッシング: noraqay.io — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 6/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar); 1 external…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
6 / 91 engine detections
レポートを開く4 community references
レポートを開くprovider verdict: clean
レポートを開く80/100
レポートを開く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
noraqay.io is an impersonation phishing site that presents itself simply as "DApp", a bare decentralized-app front with no named project behind it. It targets crypto users who expect to connect a wallet to a Web3 service. PhishDestroy first flagged it on 2026-09-17. As of 2026-10-19 the site was still online and serving its phishing content.
Pages like this copy the look and flow of a legitimate decentralized application, then prompt the visitor to connect a wallet to claim, stake, mint or verify something. The real goal is to get the victim to approve a token allowance, sign a permit or confirm a transaction that hands control of their assets to the operator. Some variants instead ask for a seed phrase under the pretext of syncing or fixing the wallet. Once a malicious approval is signed or a recovery phrase is typed in, funds can be moved out without further interaction from the victim.
On 2026-09-29, 6 of 91 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar and VIPRE. That is a modest count, but the vendors are independent of each other and of us. ScamSniffer, a blocklist focused on Web3 drainers, lists the domain alongside PhishDestroy. It also appears in 4 AlienVault OTX threat pulses, so other researchers are tracking it too.
The domain was registered on 2026-09-07 through GNAME.COM PTE. LTD., only ten days before we caught it. That short gap is typical of throwaway phishing domains. The site sits behind Cloudflare, with the edge address geolocated to Canada. That address belongs to Cloudflare's network, so it reveals nothing about where the real server is hosted.
If you connected a wallet to noraqay.io, use a token-approval checker to revoke any allowances or permits you granted it, and treat any signature you made there as suspect. If you entered a seed phrase, assume the wallet is compromised. Create a new wallet and move any remaining assets immediately. Do not return to the site to undo anything. Defenders should block the domain at DNS and proxy level, add it to wallet and browser-extension blocklists, and report it to Cloudflare and the registrar so the live page can be taken down.
Last checked
Edge-IP の評判はこのドメインに起因しません。
brit.ns.cloudflare.comjavon.ns.cloudflare.comLocation describes the IP network.
36f4d0e8561ab820970ac80fd1546ecfcdb0a400e60319bb356171016b0f142eSaved 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 noraqay.io · checked Sep 17, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
noraqay.io
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
0→2
到達可能
4 community references
View sourceNo threat flag
View source6/91 engine detections
View sourcenoraqay.io
View sourcePage captured
View sourceListed 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 ↗
noraqay.io)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.