VirusTotal
6 / 91 engine detections
보고서 열기“The Standard Reserve: Banks”
MetaMask 사칭: standardreserve.live — 콘텐츠를 사용할 수 없음. 증거 요약: VirusTotal 6/91 (alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet, Google Safe Browsing…
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
6 / 91 engine detections
보고서 열기60 det.
보고서 열기Suspicious
보고서 열기Threat flag recorded
보고서 열기4 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.live presented itself as "The Standard Reserve: Banks", a reserve-and-banking brand used to win the trust of people looking for financial or crypto services. PhishDestroy classifies it as an impersonation phishing page and flagged it on 2026-09-27, the same day the domain was registered. The site went offline on 2026-09-30, and as of 2026-10-19 its DNS is inactive and it no longer resolves.
Pages like this borrow the look and authority of a bank or reserve institution so visitors believe they are dealing with a regulated custodian. The victim is then asked to sign in, hand over personal or account details, deposit funds, or connect a crypto wallet to "access" the service. Its listing by MetaMask and SEAL points to crypto users as the intended audience. Whatever the victim types or approves goes straight to the operators: login credentials, identity data, deposited funds, or wallet permissions that let them move assets.
Six of 91 VirusTotal engines flagged the domain as of 2026-09-29: alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet, Google Safe Browsing, Gridinsoft and SOCRadar. The count is modest, but it was reached within two days of registration. Google Safe Browsing labels the site SOCIAL_ENGINEERING, which triggers browser warnings for most users. Beyond PhishDestroy, the domain sits on the MetaMask and SEAL blocklists, and it appears in four AlienVault OTX threat pulses.
Registration through Eranet International Limited and first detection fell on the same day, 2026-09-27, so the domain was put into use right away rather than aged to look established. Traffic ran through Cloudflare, Inc. at an address geolocated to Canada; that is a proxy front, so the operators' actual server stays out of view. The whole operation lasted about three days before going dark, a short lifespan typical of disposable phishing domains.
If you entered a password on this site, change it wherever you reused it and turn on app-based two-factor authentication. If you connected a wallet or signed anything, revoke token approvals with a trusted approval checker and move remaining funds to a fresh wallet if you shared a seed phrase. If you sent money or bank details, contact your bank or exchange immediately and report the incident. Defenders should block the domain, search mail and proxy logs for visits since 2026-09-27, and treat new lookalike "Standard Reserve" domains as likely relaunches.
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 평판은 이 도메인에 귀속되지 않습니다.
jo.ns.cloudflare.comrodney.ns.cloudflare.comLocation describes the IP network.
f9ccdcc70f223b83aaf0f7311892d61bb6ebc5e86ee4960c0d8916a91ebd3792Saved 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.live · 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
접속 가능→이용 불가
No flag recorded→Flag recorded
0→1
접속 가능
6/91 engine detections
View sourceThreat flag recorded
View source4 community references
View sourcePD-20260927-E2CBF6
Page captured
View sourcestandardreserve.live
View source저장된 유사 도메인 79개
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
standardreserve.live
PD-20260927-E2CBF6 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.live)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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
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.