Lompat ke laporan keamanan
Keamanan domain dan intelijen ancaman
msteam.cc favicon

msteam.cc

“Teams Meeting”

Registrar
CNOBIN INFORMATION TEC…
Resolved IP
178.16.54.253
Registered
30/09/2026
PhishDestroy assessment Kritis
Ketersediaan Konten tidak tersedia Konten tidak tersedia dalam observasi terbaru Teramati · HTTP probe
Deteksi Total Virus: 9/92 Spamhaus DBL: DBL_SPAM Daftar blokir yang disimpan cocok: 2 Label merek otomatis: Steam Domain muda: 19 berumur hari
OTX: 4 refs 16/10/2026 1 Report Sent
API
Domain ini telah ditandai sebagai berbahaya
Mesin keamanan melaporkan deteksi: 9. Daftar blokir publik yang melaporkan kecocokan: 2. Berhati-hatilah — jangan memasukkan kredensial atau informasi pribadi.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
Ringkasan laporan

Peniruan Steam: msteam.cc — Konten tidak tersedia. Ringkasan bukti: VirusTotal 9/92 (alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker)…

Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.

Source evidenceVirusTotal 9 / 92 · OTX 4 references 7 sources

VirusTotal

9 / 92 engine detections

Buka laporan

Spamhaus DBL

DBL_SPAM

Google Safe Browsing

No threat flag

Buka laporan

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Kritis
VirusTotal
9 / 92
OTX
4 community refs
Page captures
3

PhishDestroy threat report

Overview

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.

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Terdaftar View source
PhishDestroy PhishDestroy list View source
SEAL Terdaftar View source

Last checked

Tangkapan tersimpan · 3 captures

Domain details

Domain
URLScan verdict Analisis selesai score 0 report ↗
Reputasi IP abuse score 7/100 5 reports PhishingOpen ProxyWeb SpamEmail SpamPort ScanHackingSQL InjectionBad Web BotWeb App Attack checked 16/10/2026
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomaindrainerfraudlivemonthlyphishdestroyphishingscam
Registrar CNOBIN INFORMATION TEC… VN(VN)
Kontak penyalahgunaanabuse@ordertld.com, abuse@omegatech.sc
PendaftaranDibuat 30/09/2026 (19d · Very New!) — Expires 30/09/2027
Waktu hingga pertama kali tidak tersedia 3 days
Yang kami hitung Waktu yang berlalu sejak laporan penyalahgunaan pertama kali disimpan hingga pengamatan pertama bahwa konten tersebut tidak tersedia. Hal ini tidak dapat menentukan penyebabnya.
Isi setiap laporan Catatan laporan keluar yang disimpan dapat merujuk pada bukti yang tersedia pada saat itu, seperti keputusan vendor, data pendaftaran, detail hosting, klasifikasi, atau tangkapan layar. Halaman ini tidak menyimpulkan secara pasti muatan yang dikirimkan, penerimaan, pengakuan, atau tindakan oleh penerima.
Detail teknisProvenance & timestamps
Pertama Kali Terdeteksi16/10/2026
DOM Analysisanalyzed 16/10/2026score 100/100
Submitted URLhttp://msteam.cc/
Favicon Hash
ID kasus
Observed page title
Teams Meeting
Sertifikat TLS
Diterbitkan oleh Let's Encrypt / YR1 · stored validity ends in 76 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
178.16.54.253
Network ASN
AS202412
Organization
Omegatech LTD
Observed location
Amsterdam, NL

Server nama 2

  • ns1.virtualine.org
  • ns2.virtualine.org

Mail routing 1 MX record

  • msteam.ccpriority 0

Location describes the IP network.

Sertifikat TLS

Issuer
Let's Encrypt / YR1
Valid from
2026-10-06 20:04:16
Valid until
2027-01-04 20:04:15
Validity
Within stored validity dates
Collection time
2026-10-16 16:02:07 UTC
Collection source
PhishDestroy collector
Certificate fingerprint5fb23ed733546f2850c9be4d4f4c8e77ddfcf10e640c34cab0c412f81fd28ab3

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-20 08:21:37 UTC

Primary outcome DNS tidak aktif reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Tidak diketahui Probe Inconclusive 20% 2026-10-19 22:31:20 UTC
RDAP registration Tidak diketahui
Observed timeline last reachable: 2026-10-19 10:31:22 UTC current episode first observed: 2026-10-20 08:21:37 UTC observed RIP window: 2026-10-19 10:31:22 UTC → 2026-10-20 08:21:37 UTC · 21.84h midpoint 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.

Teknologi · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Laporkan Domain Ini Kirimkan bukti & bantu lindungi orang lain

Analisis VirusTotal

9 / Vendor keamanan 92 menandai domain ini
View on VT
Last analyzed Previous stored snapshot: 9 detections
alphaMountain.ai
BitDefender
CRDF
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
SOCRadar
Analisis Performa Situs

Google PageSpeed Insights — mobile performance audit of msteam.cc · checked Oct 16, 2026

100
Good
Performance
FCP
0.92s
First Contentful Paint
LCP
0.92s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.94s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://msteam.cc/
Final URL: http://msteam.cc/meeting.php
Teams Meeting
Respons
HTTP 200
HTML body
7.5 KB
Compressed
2.6 KB
Links
0 internal · 0 external
Selected response headers
Content-Type: text/html; charset=UTF-8
Content-Encoding: gzip
Security headers present
X-Frame-OptionsX-Content-Type-OptionsX-XSS-ProtectionReferrer-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 11
Connection
Keep-Alive
Content-Encoding
gzip
Content-Length
2626
Content-Type
text/html; charset=UTF-8
Date
Fri, 16 Oct 2026 14:34:17 GMT
Keep-Alive
timeout=5, max=100
Referrer-Policy
same-origin
Vary
Accept-Encoding
X-Content-Type-Options
nosniff
X-Frame-Options
SAMEORIGIN
X-XSS-Protection
1; mode=block

Values retained by the collector; long values may be shortened during collection.

Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
21.84
Estimate basis
Bounded by observations
Estimate precision
Sedang

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history11

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Tidak diketahui→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Dapat dijangkau→Tidak tersedia

  3. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  4. VirusTotal · Detection count

    8→9

  5. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

Earlier observations 6
  1. VirusTotal · Detection count

    7→8

  2. VirusTotal · Detection count

    6→7

  3. VirusTotal · Detection count

    5→6

  4. Availability monitor · Recorded state

    Tidak diketahui→redirected

    http_redirect

  5. VirusTotal · Detection count

    1→5

  6. Availability monitor · First collection record

    Dapat dijangkau

Recorded activity

6 entries
  1. AlienVault OTX

    4 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    9/92 engine detections

    View source
  4. Abuse report sent

    PD-20261016-9A6388

    abuse@ordertld.com
  5. URLScan

    Page captured

    View source
  6. Added to PhishDestroy

    msteam.cc

    View source

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

msteam.cc

Bukti & Laporan Eksternal

Snapshot bukti yang dikirim
Sent: Ledger records: 1 Case ID: PD-20261016-9A6388 Recipient: abuse@ordertld.com
PDF notice generated
Analisis Mendalam
Help & reporting

Apakah Anda Terpengaruh oleh Situs Ini?

6 evidence signal groups linked 1 stored notification records Konten tidak tersedia
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Jika Anda memasukkan kredensial akun, informasi pribadi atau pembayaran, atau mengunduh file dari domain ini, segera ambil tindakan. Di bawah ini adalah sumber daya untuk membantu Anda melaporkan insiden tersebut dan melindungi diri Anda sendiri.

Official reporting routes

Waspadalah terhadap penipu yang mengatasnamakan pemulihan! Penjahat dapat menghubungi korban lagi sambil berpura-pura menjadi penyelidik, pengacara, atau agen pemulihan. Jangan membayar biaya di muka atau membagikan kredensial. Pelajari lebih lanjut tentang penipuan dalam proses pemulihan →

Laporkan kepada Pihak Berwenang di Daerah Anda

Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.

Direktori 97 negara

Template-based draft · optional AI wording assistance requires separate consent

Draf yang dibantu AI — detail insiden diproses oleh penyedia AI · Tinjau dan kirimkan sendiri
After a phishing incident

Rekomendasi & Saran bagi Para Korban

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

Apa yang harus saya lakukan segera?

Mendesak

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Ubah semua kata sandi — email, akun Exchange, apa pun yang menggunakan kata sandi yang sama
  • Aktifkan 2FA menggunakan aplikasi otentikator (bukan SMS). Nonaktifkan pemulihan berbasis SMS
  • Kartu pembeku jika Anda telah memasukkan detail perbankan di situs phishing tersebut

Informasi apa saja yang sebaiknya saya kumpulkan untuk laporan saya?

Pedoman FBI

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.
  • Tanggal dan waktu yang tepat — dari setiap transaksi dan kontak pertama dengan penipu
  • Tangkapan layar — situs web penipuan, pesan obrolan, email, transaksi dompet digital, media sosial
  • Semua URL & domain digunakan oleh penipu (termasuk msteam.cc)
  • Komunikasi — email, pesan teks, nomor telepon, dan nama pengguna yang digunakan oleh penipu tersebut

Meskipun kamu belum mengetahui semua detailnya — tetap saja ajukan laporan. Informasi yang tidak lengkap tetap dapat membantu penyelidikan.

Ke mana saya harus melaporkan penipuan ini?

  • FBI IC3 — Pusat Pengaduan Kejahatan Internet (Laporan tingkat federal AS)
  • Europol — Pelaporan kejahatan siber di Eropa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Polisi setempat — membuat catatan resmi, meskipun mereka tidak dapat bertindak segera

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Situs web palsu — salinan yang persis sama dengan situs asli, dengan domain yang sedikit diubah
  • Pemotongan babi — kepercayaan yang dibangun selama beberapa minggu melalui Telegram/WhatsApp/aplikasi kencan, lalu uangnya dicuri
  • Penipuan pemulihan — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Penipuan yang didukung oleh kecerdasan buatan — deepfakes, serangan phishing otomatis, dan situs yang dihasilkan oleh kecerdasan buatan (AI) yang membuat penipuan semakin sulit dideteksi

Bagaimana cara saya melindungi diri di masa depan?

  • Tandai situs resmi — jangan pernah mengklik tautan dari email, pesan langsung (DM), atau iklan
  • Memverifikasi domain — periksa PhishDestroy Sebelum berinteraksi. Periksa HTTPS, ejaan, dan usia domain
  • "Terlalu bagus untuk jadi kenyataan" = penipuan — imbal hasil yang dijamin, dukungan dari selebriti, tenggat waktu yang mendesak

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Tetap Terinformasi, Tetap Aman

Pantau ancaman secara langsung atau ajukan keberatan terhadap daftar ini jika Anda yakin ini merupakan false positive

Pemberitahuan Ancaman Real-Time Ajukan Banding Terhadap Iklan Ini
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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Sematkan Laporan Ini

Bagikan informasi ancaman ini di situs web atau blog Anda

embed.html
<iframe
  src="https://phishdestroy.io/id/embed/domain/msteam.cc"
  title="PhishDestroy threat report for msteam.cc"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>