VirusTotal
9 / 92 engine detections
Ouvrir le rapport“Teams Meeting”
Usurpation de Steam: msteam.cc — Contenu indisponible. Résumé des preuves: VirusTotal 9/92 (alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint…
L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.
9 / 92 engine detections
Ouvrir le rapportDBL_SPAM
Scan report
Ouvrir le rapport4 community references
Ouvrir le rapportprovider verdict: clean
Ouvrir le rapportNo threat flag
Ouvrir le rapportNo malicious flag
Ouvrir le rapportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
msteam.cc is an impersonation phishing page that mimics Steam. It targets Steam gamers and account holders. PhishDestroy first observed the domain on 2026-10-16. The site remains alive and returns a reachable redirect as of 2026-10-19.
The page is titled “Teams Meeting” but displays Steam branding and login fields. Victims are prompted to enter their Steam username, password and possibly Steam Guard codes, believing they are joining a meeting. Collected credentials let attackers hijack the account, potentially draining linked wallet balances or using the account for scams.
VirusTotal flagged the domain in 9 of 92 scanners, including AlphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker, Fortinet, G‑Data, Gridinsoft. PhishDestroy, MetaMask and SEAL have added it to their blocklists, and Spamhaus lists it as DBL_SPAM. OTX reports four pulses referencing the same impersonation activity. The breadth of detections confirms the phishing nature.
The domain was registered on 2026-09-30 through CNOBIN INFORMATION TECHNOLOGY LIMITED. It resolves to 178.16.54.253, part of the OMEGATECH-AS network operated by Omegatech LTD in the Netherlands. The site uses a Let’s Encrypt / YR1 certificate, indicating the operators obtained a free TLS cert to appear legitimate.
Anyone who entered Steam credentials on msteam.cc should immediately change their Steam password and enable Steam Guard two‑factor authentication. Review the account’s recent activity, remove any unknown devices, and consider revoking any linked third‑party app authorizations. Organizations should block msteam.cc at the DNS and proxy layers and add it to phishing detection feeds. Educate users to verify URLs before entering login details, especially when a page title such as “Teams Meeting” does not match the expected service.
Last checked
ns1.virtualine.orgns2.virtualine.orgmsteam.ccpriority 0Location describes the IP network.
5fb23ed733546f2850c9be4d4f4c8e77ddfcf10e640c34cab0c412f81fd28ab3Saved 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.
mail.msteam.ccDomain recordwww.msteam.ccDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of msteam.cc · checked Oct 16, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://msteam.cc/http://msteam.cc/meeting.phpContent-Type: text/html; charset=UTF-8Content-Encoding: gzipKeep-Alivegzip2626text/html; charset=UTF-8Fri, 16 Oct 2026 14:34:17 GMTtimeout=5, max=100same-originAccept-EncodingnosniffSAMEORIGIN1; mode=blockValues retained by the collector; long values may be shortened during collection.
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.
Inconnu→dns_inactive
dns_nxdomain
Accessible→Indisponible
Inconnu→redirected
http_redirect
8→9
Inconnu→redirected
http_redirect
7→8
6→7
5→6
Inconnu→redirected
http_redirect
1→5
Accessible
4 community references
View sourceNo threat flag
View source9/92 engine detections
View sourcePD-20261016-9A6388
Page captured
View sourcemsteam.cc
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
msteam.cc
PD-20261016-9A6388 Recipient: abuse@ordertld.com Si vous avez saisi des informations d'identification de compte, des informations personnelles ou de paiement, ou téléchargé un fichier à partir de ce domaine, agissez immédiatement. Vous trouverez ci-dessous des ressources pour vous aider à signaler l'incident et à vous protéger.
Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.
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 ↗
msteam.cc)Même si vous ne disposez pas de tous les détails — déposer quand même une plainte. Même des informations partielles peuvent aider les enquêtes.
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
Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique
Scanner maintenantSignalez les domaines suspects à notre base de données des menaces — protégez la communauté
SignalerRapports de phishing récents et changements de disponibilité observés
SurveillerSurveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif
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.