VirusTotal
6 / 91 engine detections
レポートを開く“The Standard Reserve: Banks”
MetaMaskなりすまし: standardreserve.lol — コンテンツが利用できません. 証拠の概要: VirusTotal 6/91 (alphaMountain.ai, Forcepoint ThreatSeeker, Google Safe Browsing, Gridinsoft…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
6 / 91 engine detections
レポートを開く60 det.
レポートを開くSuspicious
レポートを開くThreat flag recorded
レポートを開く3 community references
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
standardreserve.lol is an impersonation phishing page that presented itself as The Standard Reserve, with a page titled "The Standard Reserve: Banks". It targeted people who would recognise that name, including crypto users, which is why wallet-focused blocklists picked it up. PhishDestroy flagged it on 2026-09-27, the same day the domain was registered. The site has been offline since 2026-09-30, and as of 2026-10-19 its DNS no longer resolves.
Impersonation pages borrow a trusted brand's name and look so visitors act without second-guessing. The "Banks" title suggests a page dressed up as a banking or partner-institution section, the kind of place where a visitor expects to log in, verify an account or link funds. Whatever the victim types or approves goes to the operators. That can mean login credentials, personal details, or, for anyone who connected a wallet, access to their crypto. The cheap .lol domain and its few days online fit a burn-and-replace campaign rather than a lasting site.
Google Safe Browsing classified the site as SOCIAL_ENGINEERING, its category for deceptive pages that trick users into handing something over. On VirusTotal, 6 of 91 engines flagged it as of 2026-09-29: alphaMountain.ai, Forcepoint ThreatSeeker, Google Safe Browsing, Gridinsoft, Lionic and SOCRadar. That is a modest count, but typical for a domain caught within days of going live. MetaMask and SEAL list it alongside PhishDestroy, and three AlienVault OTX pulses reference it, which shows other researchers tracked it independently.
The domain was registered through Eranet International Limited on 2026-09-27 and was detected that same day. It went dark three days later, a lifespan that points to a short-lived phishing run. Traffic went through Cloudflare, Inc., which hides the real origin server, and the address geolocates to Canada. The free Let's Encrypt certificate gave it a padlock icon, which proves nothing about who runs a site.
If you entered a username, password or one-time code on this page, change that password wherever you use it and reset two-factor authentication. Then review recent account activity with the real institution, contacting them through channels you already trust. If you connected a wallet or signed anything, revoke token approvals granted around that time. Move remaining assets to a fresh wallet if you shared a seed phrase. Defenders should block the domain, search mail and proxy logs for visits between 2026-09-27 and 2026-09-30, and watch for lookalike Standard Reserve domains, because takedown-and-replace is common for this kind of operation.
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 の評判はこのドメインに起因しません。
henry.ns.cloudflare.comjean.ns.cloudflare.comLocation describes the IP network.
2b556d744d1708e53f4bf5308cb0247bbdc5f09b009a81dec6e069bee3484a3eSaved 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 standardreserve.lol · checked Sep 27, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
到達可能→利用不可
No flag recorded→Flag recorded
0→1
到達可能
Threat flag recorded
View source6/91 engine detections
View source3 community references
View sourcePD-20260927-9A77DD
Page captured
View sourcestandardreserve.lol
View source保存された類似ドメイン:79 件
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
standardreserve.lol
PD-20260927-9A77DD Recipient: support@eranet.com, support@tnet.hk, info@todaynic.com アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
standardreserve.lol)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.