teams.surf is an impersonation phishing site whose name borrows the word "teams" to look like a legitimate service. MetaMask's and SEAL's blocklists both carry it, which points to crypto users as the main target. PhishDestroy first saw it on 2026-08-26, and it was still online and serving content on 2026-10-19.
How the scam works
Impersonation pages copy a familiar brand or product so visitors trust them. They then ask for a login, a recovery phrase, a download, or a wallet connection that hands control to the operator. Victims can lose account access, or the funds in a wallet whose seed phrase or signing approvals they gave away. The page currently shows the title "Index of /", a plain directory listing, while we classify the domain as an impersonation phishing page.
Evidence
On 2026-10-03, 11 of 91 VirusTotal engines flagged the domain. They include alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft and Kaspersky. That is a minority of engines, but the agreement among several established vendors is meaningful. Spamhaus lists the domain in its DBL under the phishing category. MetaMask, SEAL and PhishDestroy all block it. Three AlienVault OTX threat pulses also reference it, so other researchers have tracked it independently.
Infrastructure
The domain was registered through NameCheap, Inc. on 2026-08-24, just two days before PhishDestroy detected it. That short gap is typical of throwaway domains put to use right after purchase. It resolves to 198.54.116.104 on Namecheap's network in the US, so the domain and hosting come from the same provider.
What to do
Do not enter credentials, seed phrases or private keys on teams.surf, and do not run anything it offers for download. If you typed in a password, change it everywhere you reused it and turn on app-based 2FA. If you revealed a recovery phrase, treat that wallet as compromised and move the funds to a new wallet created on a clean device. If you connected a wallet or signed something, revoke the approvals you granted. Defenders should block the domain and its IP at DNS and proxy level, and search logs for any visits since 2026-08-26.
DOM Analysisanalyzed 2026年9月20日score 100/1001 brand signal
Favicon Hash
ICANN OVERSIGHT
認定と RAA の背景
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
Certificate fingerprint887b220a5d0166c1f4e3050e0c52308e62c6c57a70955ae9929bd84a258800d6Certificate names · 1 SANs
www.teams.surf
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationコンテンツ公開中Ordinary HTTP content served90%2026-10-20 10:07:30 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-20 10:07:30 UTClast content: 2026-10-20 10:07:30 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Recorded subdomains1
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.teams.surfDomain record
The original observation time is not recorded for these hostnames.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
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.
(US)
