VirusTotal
6 / 89 engine detections
レポートを開く“Stake 新用户活动”
Stakeなりすまし: stake.taipei — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 6/89 (BitDefender, CRDF, ESET, G-Data, Gridinsoft); URLScan malicious verdict…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
6 / 89 engine detections
レポートを開くDBL_PHISH
悪意あり
レポートを開く4 community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
stake.taipei is an impersonation phishing page posing as Stake, the cryptocurrency casino and sportsbook. Its page title, "Stake 新用户活动" ("Stake new user event"), shows it is aimed at Chinese-speaking gamblers who are drawn in by a sign-up promotion. PhishDestroy first flagged it on 2026-09-01. As of 2026-10-19 the site was still online and serving its phishing content.
Fake "new user" campaigns copy a gambling brand's look and offer a bonus that supposedly unlocks after you register, log in or make a first deposit. The visitor is steered into typing their Stake login details into the lookalike page or sending crypto to a deposit address the operators control. Stolen credentials let the scammers empty the real account, and any deposit made on the fake site goes straight to them. No bonus is ever paid.
Six of 89 VirusTotal engines flagged the domain when it was checked on 2026-09-13: BitDefender, CRDF, ESET, G-Data, Gridinsoft and SOCRadar. That count is modest, so many security tools may not warn a visitor yet. urlscan.io rated the page malicious and recognized Stake branding on it. Spamhaus lists the domain in its DBL as a phishing domain, and the MetaMask and SEAL blocklists carry it alongside PhishDestroy. It also appears in four AlienVault OTX threat pulses.
The domain was registered on 2026-08-30 through Gname.com Pte. Ltd. and was flagged just two days later, which fits a site built for a short phishing campaign rather than a long-running business. The ".taipei" extension matches the Chinese-language lure. Traffic runs through Cloudflare's network, so the listed Canadian location reflects Cloudflare's edge and not necessarily where the real server sits.
If you logged in on stake.taipei, change your Stake password at once from the official site, turn on two-factor authentication, and check your account for withdrawals or settings you did not make. Change the password anywhere else you used the same one. If you sent crypto to an address shown on this page, treat those funds as lost to scammers, contact Stake support and report the theft. Do not chase the promised bonus or pay any "activation" deposit. Defenders should block the domain at DNS and web proxies and watch for further Stake-themed lookalike domains.
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 の評判はこのドメインに起因しません。
jo.ns.cloudflare.comLocation describes the IP network.
72eb6ff1bf15be7ee0770441b542e13161e94dac1470cd58235813a6cb468a80Saved 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 stake.taipei · checked Sep 1, 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.
stake.taipei
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
到達可能
4 community references
View sourceNo threat flag
View source6/89 engine detections
View sourcestake.taipei
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 ↗
stake.taipei)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.