VirusTotal
11 / 91 engine detections
보고서 열기“Index of /”
Steam 사칭: teams.surf — 마지막으로 알려진 활성 (HTTP 200). 증거 요약: VirusTotal 11/91 (alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet); Spamhaus…
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
11 / 91 engine detections
보고서 열기DBL_PHISH
3 community references
보고서 열기provider verdict: clean
보고서 열기No threat flag
보고서 열기No malicious flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
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.
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.
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.
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.
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.
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.
dns1.namecheaphosting.commx1-hosting.jellyfish.systemspriority 5mx2-hosting.jellyfish.systemspriority 10mx3-hosting.jellyfish.systemspriority 20Location describes the IP network.
887b220a5d0166c1f4e3050e0c52308e62c6c57a70955ae9929bd84a258800d6www.teams.surfSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.teams.surfDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of teams.surf · checked Sep 2, 2026
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.
teams.surf
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
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
redirected→live_content
content_served
알 수 없음→redirected
http_redirect
이용 불가→접속 가능
접속 가능→이용 불가
접속 가능
3 community references
View source11/91 engine detections
View sourceNo threat flag
View sourceteams.surf
View sourceListed 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 ↗
teams.surf)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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.