VirusTotal
3 / 89 engine detections
レポートを開く“LOBSTR — Simple, Secure Crypto Wallet”
ブロックリスト掲載ドメイン: lobstr-web-1m0.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 3/89 (ChainPatrol, alphaMountain.ai, Forcepoint ThreatSeeker); 2…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
3 / 89 engine detections
レポートを開くno 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
lobstr-web-1m0.pages.dev is an impersonation phishing page that copied the LOBSTR wallet brand under the title "LOBSTR — Simple, Secure Crypto Wallet". It targeted people looking for the LOBSTR wallet, which is mainly used to hold Stellar assets. PhishDestroy first flagged it on 2026-09-06. The site has been offline since 2026-09-16 and was blocked by its hosting provider, which was still the case on 2026-10-19.
The page reused LOBSTR's own tagline so that a visitor arriving from a search result, ad or chat link would believe they had reached the official wallet. Pages like this usually invite the user to "log in", "restore" or "sync" a wallet. The goal is to get the 12- or 24-word recovery phrase or the Stellar secret key typed into a form the operators control. Anyone who holds that secret can rebuild the wallet on their own device and move every asset out, and on-chain transfers cannot be reversed.
On 2026-09-17, three of 89 VirusTotal engines flagged the address: ChainPatrol, alphaMountain.ai and Forcepoint ThreatSeeker. That is a low count, so most generic scanners would have let it through. The more telling signal comes from crypto-focused defenders. MetaMask's blocklist and SEAL both list the domain alongside PhishDestroy, which means wallet-security teams reached the same verdict independently.
The site ran as a free Cloudflare Pages project rather than on a purchased domain. It was created on 2026-08-28, nine days before PhishDestroy detected it. It resolved to Cloudflare's network with a Canadian geolocation and used a standard Google Trust Services certificate, so the padlock in the browser meant nothing about legitimacy. The pages.dev setup let the operators spin up a branded-looking address at no cost and abandon it within about three weeks.
If you entered a LOBSTR recovery phrase or secret key on this page, treat the wallet as compromised. Create a new wallet on a clean device from the official app and move any remaining funds to it immediately. Never import the exposed phrase anywhere again. If you only browsed without entering anything, no action is needed, but reach LOBSTR only through its official app store listings or a saved bookmark. Defenders should block lookalike pages.dev and similar free-hosting subdomains that carry wallet brand names, and report new ones to the hosting provider and to wallet blocklists such as MetaMask and SEAL.
Last checked
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
1879b02016b4c7c69d0a2f3b0020cbb063b51ad142e0b49c093f73ec8024394dSaved 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 lobstr-web-1m0.pages.dev · checked Sep 15, 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
lobstr-web-1m0.pages.dev
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 source3/89 engine detections
View sourcelobstr-web-1m0.pages.dev
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 ↗
lobstr-web-1m0.pages.dev)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.