VirusTotal
15 / 91 engine detections
レポートを開く“Base Web3 Extension”
Baseなりすまし: baselabs.global — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 15/91 (ChainPatrol, alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF); Google…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
15 / 91 engine detections
レポートを開くThreat flag recorded
レポートを開くDBL_SPAM
checked — no match recorded
12 community references
レポートを開くprovider verdict: clean
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
This domain, baselabs.global, is classified as a high-risk brand impersonation threat specifically targeting the Across Protocol, a decentralized bridging platform. The site masqueraded as a legitimate Web3 extension under the title 'Base Web3 Extension,' attempting to deceive users into interacting with fraudulent smart contracts or disclosing sensitive credentials. Brand impersonation of this nature typically aims to exploit trust in established blockchain infrastructure, increasing the likelihood of financial loss or unauthorized access to digital assets. Analysis indicates the domain was registered on October 18, 2025, through Hosting Concepts B.V. d/b/a Registrar.eu, a registrar frequently observed in malicious infrastructure deployments. It resolved to the IP address 62.60.135.13, located in the Netherlands, and utilized a Let's Encrypt SSL certificate (R12) to present a false sense of security. The domain appears on one security blocklist and is flagged by Google Safe Browsing as phishing. VirusTotal detection metrics reveal that 18 out of 95 security vendors marked the domain as malicious, a relatively low but notable detection rate that suggests either evasion techniques or recent deployment. The domain has since been taken offline, though residual risk remains for users who may have interacted with it prior to its deactivation. Mitigation against brand impersonation threats of this nature requires multi-layered defenses. Users should verify domain authenticity by cross-referencing official communication channels, such as the Across Protocol’s verified social media or documentation, before interacting with any Web3-related services. Organizations should implement domain monitoring to detect newly registered lookalike domains and enforce blocklisting of known malicious IPs, such as 62.60.135.13, at the network perimeter. Additionally, security teams should prioritize user education on recognizing phishing indicators, including mismatched SSL certificates, suspicious page titles, and domains registered through high-risk registrars. Proactive measures, such as deploying browser-based anti-phishing extensions and enforcing strict transaction verification protocols, can further reduce exposure to similar threats.
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.
ns1.dynamicbackend.comns2.dynamicbackend.comLocation describes the IP network.
8177a617a38be4f22e7f8b1e4f79b2c9948c190a38dde8c37cf39822343881c4Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
alive_content: raw=ok; http=200; via=https_proxy; server=openresty
baselabs.global
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→live_content
content_served
No flag recorded→Flag recorded
不明→live_content
content_served
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
https://radar.cloudflare.com/scan/cec44b40-9c09-44bd-acc1-cc9268306855
12 community references
View sourceThreat flag recorded
View source15/91 engine detections
View sourcePage captured
View sourcebaselabs.global
View sourceコミュニティ報告:1 件
カテゴリPHISHING
Scammers uploaded a fake Coinbase wallet to the Chrome Web Store, which led to the leakage of my private key. Whenever my wallet received funds, they were immediately transferred away by the scammers. This Chrome extension is still available in the Chrome Web Store and even has
コミュニティの 1 人が報告・初回確認 2025年12月13日
“Scammers uploaded a fake Coinbase wallet to the Chrome Web Store, which led to the leakage of my private key. Whenever my wallet received funds, they were immediately transferred away by the scammers. This Chrome extension is still available in the Chrome Web Store and even has a very high rating. The associated website is also highly deceptive. I hope this fraudulent website and extension can be taken down as soon as possible to prevent more people from being victimized.”
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 ↗
baselabs.global)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.