trezor.locker is a phishing domain that borrows the Trezor name to target owners of Trezor hardware wallets. PhishDestroy first flagged it on 2026-08-14, a single day after registration. The site has been offline since 2026-09-10, and its DNS was still inactive when last checked on 2026-10-19.
How the scam works
Trezor impersonation sites typically copy the brand's look and push visitors through a fake setup, firmware update or "wallet recovery" step. That step asks for the 12- or 24-word recovery seed. Anyone who types those words hands over full control of the wallet, and the attacker can then empty it from any device. The page title served on the domain read "PHP 7.4.33 - phpinfo()", a default server diagnostics page, while PhishDestroy classified the domain as a Trezor impersonation.
Evidence
Detection was limited but came from several independent sources. VirusTotal showed 6 of 91 engines flagging the domain on 2026-08-25: alphaMountain.ai, Chong Lua Dao, Forcepoint ThreatSeeker, Fortinet, Gridinsoft and SOCRadar. Besides PhishDestroy, the wallet-focused blocklists of MetaMask and SEAL list it, so users of those protections were warned. It also appears in 4 AlienVault OTX threat pulses, which means other researchers tracked it as well.
Infrastructure
The domain was registered on 2026-08-13 through Gname.com Pte. Ltd. and was caught the next day. That fast turnaround points to a disposable domain registered for a short campaign. It resolved to 43.108.86.51 on the Alibaba (US) Technology Co., Ltd. network, with the server located in South Korea. The ".locker" extension paired with the brand name is meant to sound like secure storage, a lure aimed at security-minded hardware wallet users.
What to do
If you entered your Trezor recovery seed on this site, treat that wallet as compromised. Set up a new wallet with a freshly generated seed and move any remaining funds to it right away. Trezor never asks for your seed on a website, so any page that does is a scam. If you only visited and entered nothing, you need no further action beyond avoiding the domain. Defenders should block trezor.locker at DNS and proxy level and add lookalike Trezor domains on unusual extensions to their monitoring.
등록 정보생성됨 2026년 8월 13일 (66d · New)—Expires 2027년 8월 13일
최초 이용 불가까지 걸린 시간27 days
집계 기준
처음 저장된 악용사례 신고부터 콘텐츠를 사용할 수 없다는 첫 번째 관찰까지의 경과 시간입니다. 이것은 원인을 확립하지 못합니다.
각 보고서에 포함된 내용
저장된 발신 보고서 기록은 공급업체 평가, 등록 데이터, 호스팅 세부 정보, 분류 또는 스크린샷과 같이 당시 사용 가능한 증거를 참조할 수 있습니다. 이 페이지는 전달된 정확한 페이로드, 수신, 확인 또는 수신자의 작업을 추론하지 않습니다.
기술 세부 정보Provenance & timestamps
최초 발견2026년 8월 14일
Submitted URLhttp://trezor.locker/
Favicon Hash
사건 ID
ICANN OVERSIGHT
인증 및 RAA 상황
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
Primary outcomeDNS 비활성reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation알 수 없음Probe Inconclusive20%2026-10-19 01:12:24 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-08-19 22:15:56 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-08-19 22:15:56 UTC → 2026-09-30 16:14:55 UTC · 1,001.98hmidpoint estimate ≈ 2026-09-09 19:15:25 UTC · precision very low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Template-based draft · optional AI wording assistance requires separate consent
AI 지원 초안 - 사고 세부정보는 AI 제공업체에서 처리됩니다. · 직접 검토하고 제출하세요.
After a phishing incident
피해자를 위한 권고 사항 및 조언
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.
모든 비밀번호 변경 — 이메일, 익스체인지 계정 등, 동일한 비밀번호를 사용하는 모든 것
2단계 인증 활성화 인증 앱(SMS 제외)을 사용합니다. SMS 기반 복구 기능을 비활성화하세요.
카드 동결 피싱 사이트에 은행 계좌 정보를 입력한 경우
보고서를 작성하기 위해 어떤 정보를 수집해야 할까요?
FBI 지침
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
정확한 날짜 및 시간 — 각 거래 내역 및 사기범과의 첫 접촉 시점
스크린샷 — 사기 웹사이트, 채팅 메시지, 이메일, 지갑 거래, 소셜 미디어
모든 URL 및 도메인 사기꾼이 사용한 (다음과 같은 것들을 포함하여 trezor.locker)
커뮤니케이션 — 사기꾼이 사용한 이메일, 문자, 전화번호, 사용자 이름
비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
지역 경찰 — 비록 당장 조치를 취할 수는 없더라도 공식 기록을 남깁니다
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
가짜 웹사이트 — 도메인을 약간만 변경한, 정식 사이트와 픽셀 단위로 완벽하게 일치하는 복제 사이트
pig butchering — Telegram·왓츠앱·데이트 앱을 통해 몇 주에 걸쳐 신뢰를 쌓은 뒤, 돈을 훔쳐갔다
회복 사기 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI를 이용한 사기 — 딥페이크, 자동화된 피싱, AI로 생성된 사이트 등으로 인해 사기 행각을 적발하기가 더 어려워지고 있다
앞으로 어떻게 하면 스스로를 지킬 수 있을까요?
공식 사이트 즐겨찾기 추가 — 이메일, DM 또는 광고에 포함된 링크는 절대 클릭하지 마세요
도메인 확인 — 확인하기 PhishDestroy 상호작용을 시작하기 전에 HTTPS, 맞춤법, 도메인 등록 기간을 확인하세요.
About this reportSources, observation dates and corrections
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.
(KR)
