VirusTotal
8 / 89 engine detections
보고서 열기“Suspected Phishing | Cloudflare”
피싱: briidge-base.pages.dev — 연결 가능 · 액세스가 제한됨 (HTTP 403). 증거 요약: VirusTotal 8/89 (alphaMountain.ai, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data); Google…
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
8 / 89 engine detections
보고서 열기Threat flag recorded
보고서 열기no community references
보고서 열기provider verdict: clean
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
briidge-base.pages.dev is an impersonation phishing page. Its name, with a doubled "i" in "bridge", is built to pass for a bridge to the Base network at a glance, so it targets crypto users moving assets between chains. PhishDestroy first saw it on 2026-09-03. The site has been offline since 2026-09-14, and on 2026-10-19 it was still dead, with its content blocked by the hosting provider.
Fake bridge pages copy the look of a real cross-chain tool and ask visitors to connect a wallet and approve a transfer. The prompts that appear are typically token approvals or signatures that hand control of the victim's assets to the operator, or a direct transfer to an address the scammer controls. Bridge users are attractive targets because they expect to sign several transactions and often move large balances at once. The page title now reads "Suspected Phishing | Cloudflare", which is the provider's warning page. That differs from the bridge impersonation we classified.
On 2026-09-16, VirusTotal showed 8 of 89 engines flagging the domain. The vendors were alphaMountain.ai, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Google Safe Browsing, Sophos and VIPRE. Google Safe Browsing lists it under SOCIAL_ENGINEERING, so Chrome and other browsers that use that feed warn visitors. Beyond PhishDestroy, it appears on the MetaMask and SEAL blocklists, two wallet-focused feeds whose listings point directly at crypto theft.
The page was deployed as a free subdomain on Cloudflare Pages rather than as a registered domain. A setup like that takes minutes and costs nothing, which makes it easy to replace once blocked. It resolved to 172.66.47.71 on Cloudflare, Inc.'s network, geolocated to CA. It stayed online for about eleven days after PhishDestroy first saw it, until the provider pulled its content.
If you connected a wallet to this page, review its token approvals with a revocation tool and cancel any granted to contracts or addresses you do not recognize. If you signed a transfer or approval, move remaining funds to a fresh wallet. If you typed in a seed phrase, treat the wallet as compromised and abandon it. Always reach bridges through bookmarks or the project's official channels, never through search ads or links in direct messages. Defenders should block the domain and watch for similar misspelled "bridge" and "base" subdomains on free hosting platforms.
Last checked
Edge-IP 평판은 이 도메인에 귀속되지 않습니다.
Location describes the IP network.
Google PageSpeed Insights — mobile performance audit of briidge-base.pages.dev · checked Sep 14, 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.
알 수 없음→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
4→8
접속 가능→이용 불가
No flag recorded→Flag recorded
접속 가능
Threat flag recorded
View source8/89 engine detections
View sourcebriidge-base.pages.dev
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
briidge-base.pages.dev
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 ↗
briidge-base.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
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.