VirusTotal
7 / 89 engine detections
レポートを開く“Security Portal”
Trezorなりすまし: trezor.protection-update-device.online — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 7/89 (alphaMountain.ai, Chong Lua Dao, Forcepoint…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
7 / 89 engine detections
レポートを開くDBL_PHISH
no community references
レポートを開くprovider verdict: clean
レポートを開く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
trezor.protection-update-device.online is an impersonation phishing page that poses as Trezor, borrowing the brand as a subdomain in front of a hostname built around "protection" and "update device". It targets owners of Trezor hardware wallets who might believe their device needs an urgent security fix. PhishDestroy first saw it on 2026-08-09. As of 2026-10-19 the domain was still alive and serving a redirect, so it remains a live risk.
The page presents itself as a "Security Portal", a framing that fits the classic Trezor lure: a warning that the device is compromised or out of date, followed by a "verification" or "recovery" step. In schemes of this type, that step asks the victim to type in their recovery seed phrase, which gives the attacker full control of every account the wallet protects. Once the phrase is submitted, funds can be swept to the attacker without the physical device ever being touched. Trezor never asks for a recovery phrase on a website, so any page that does is fraudulent.
On 2026-09-17, 7 of 89 VirusTotal engines flagged the domain: alphaMountain.ai, Chong Lua Dao, Forcepoint ThreatSeeker, Fortinet, LevelBlue, PhishFort and SOCRadar. That count is modest, but several of these vendors specialise in phishing and brand-abuse detection. Spamhaus lists the domain in its DBL as DBL_PHISH, which is an independent phishing verdict, and the domain is on the PhishDestroy blocklist.
The domain was registered through NameCheap, Inc. on 2026-08-02, only seven days before PhishDestroy detected it. That short gap is typical of a site created for a single campaign. It is hosted on Namecheap, Inc. network space in the US. Its certificate comes from SSL.com, so visitors see a valid padlock even though the site is fraudulent.
If you entered your recovery seed on this site, treat the wallet as compromised. Set up a new wallet with a fresh seed, ideally after resetting your Trezor, and move any remaining funds there right away. Never reuse the exposed phrase. If you only visited the page, close it and use Trezor's official software for any updates. Security teams should block the domain and the protection-update-device.online parent at DNS and proxy level and report the page to the registrar and hosting provider for takedown.
For the registrable domain protection-update-device.online behind this subdomain, 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.
dns2.namecheaphosting.comLocation describes the IP network.
5b6e2aa6c027c5e7b9eff2a49348a7ee8ff336151999adf7634fb39b196dee90Saved 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 trezor.protection-update-device.online · checked Aug 14, 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.
trezor.protection-update-device.online
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
利用不可→到達可能
到達可能→利用不可
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
live_content→redirected
http_redirect
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
到達可能
Page captured
View source7/89 engine detections
View sourceNo threat flag
View sourcetrezor.protection-update-device.online
View source保存された類似ドメイン:74 件
コミュニティ報告:2 件
カテゴリIMPERSONATION
Brand abuse: phishing, credential harvesting, impersonation, impersonating Trezor
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 ↗
trezor.protection-update-device.online)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.