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.
How the scam works
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.
Evidence
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.
Infrastructure
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.
What to do
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-19 22:31:20 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-19 10:31:22 UTCcurrent episode first observed: 2026-10-20 08:21:37 UTCobserved RIP window: 2026-10-19 10:31:22 UTC → 2026-10-20 08:21:37 UTC · 21.84hmidpoint estimate ≈ 2026-10-19 21:26:29 UTC · precision medium · basis bounded
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 subdomains2
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
mail.msteam.ccDomain record
www.msteam.ccDomain record
The original observation time is not recorded for these hostnames.
使用技術 · 2 identified
P
PHP
Programming languages
PHP is a general-purpose scripting language used for web development.
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.
(VN)
