VirusTotal
14 / 89 engine detections
レポートを開く“Phantom 💎 Wallet”
Phantomなりすまし: phant-tomiowalet.gitbook.io — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 14/89 (ChainPatrol, alphaMountain.ai, BitDefender, ESET, Emsisoft); 2…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
14 / 89 engine detections
レポートを開く悪意あり
レポートを開く15/100
レポートを開く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
phant-tomiowalet.gitbook.io was an impersonation phishing page dressed up as Phantom, the popular self-custody crypto wallet. It targeted Phantom users through a GitBook-hosted page titled "Phantom 💎 Wallet" under a deliberately garbled subdomain. PhishDestroy first saw it on 2026-09-11. The site has been offline since 2026-09-14, its content has been blocked by the hosting provider, and it was still down when last checked on 2026-10-19.
Scams like this exploit the credibility of documentation platforms. A GitBook page looks like official help material, so a victim searching for wallet support or clicking a shared link may believe they are on a genuine Phantom resource. These pages usually push the visitor to "restore", "verify" or "sync" their wallet by typing in a secret recovery phrase or private key, or by connecting the wallet and approving a request. Anyone who hands over a recovery phrase gives the attacker full control of the wallet, and the assets can be moved out within minutes.
14 of 89 VirusTotal engines flagged the page on 2026-09-12, one day after PhishDestroy first saw it. The vendors include crypto-focused ChainPatrol alongside BitDefender, ESET, Kaspersky, Fortinet, Emsisoft, G-Data and alphaMountain.ai. MetaMask's blocklist and the SEAL security alliance list it along with PhishDestroy, so wallet users relying on those protections should have received a warning.
The page sat on a subdomain of gitbook.io, a legitimate publishing platform. The 2014-03-30 registration and the Cloudflare, Inc. registrar belong to GitBook's own domain, so the domain's age tells you nothing about the operator. Traffic was served through Cloudflare's network from an address located in Canada. The operator never had to register or host anything themselves, which is why provider-side blocking took the page down within days.
If you entered a recovery phrase or private key on this page, treat that wallet as compromised. Create a new wallet with a fresh phrase on a clean device and move any remaining assets to it immediately. If you only connected your wallet or signed a request, review and revoke token approvals and connected sites, and watch for unexpected transactions. Remember that Phantom will never ask for your recovery phrase on a website. Security teams should block lookalike Phantom subdomains on documentation and site-builder platforms and report new ones to the hosting provider for fast removal.
Last checked
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
d76aa1094c3d1ca19014ac824313b04e833289dec61fbca06aa6f92bad9464adgitbook.ioSaved 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 phant-tomiowalet.gitbook.io · checked Sep 11, 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.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
phant-tomiowalet.gitbook.io
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
到達可能→利用不可
No threat flag
View source14/89 engine detections
View sourcephant-tomiowalet.gitbook.io
View source保存された類似ドメイン:3 件
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 ↗
phant-tomiowalet.gitbook.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.