Lompat ke laporan keamanan
Keamanan domain dan intelijen ancaman
linkedpaycheck.com favicon

linkedpaycheck.com

“Linkedpay - карты и платежи в Telegram”

Registrar
Cloudflare
Resolved IP
104.21.65.148
Registered
09/08/2026
PhishDestroy assessment Kritis
Ketersediaan Terakhir diketahui aktif Pengamatan keterjangkauan tersimpan terbaru Teramati · HTTP probe
Deteksi Total Virus: 5/92 Daftar blokir yang disimpan cocok: 2 Label merek otomatis: Telegram
OTX: 4 refs 27/09/2026 CDN
API
Domain ini telah ditandai sebagai berbahaya
Mesin keamanan melaporkan deteksi: 5. 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
Ringkasan laporan

Peniruan Telegram: linkedpaycheck.com — Terakhir diketahui aktif (HTTP 200). Ringkasan bukti: VirusTotal 5/92 (alphaMountain.ai, Ermes, Forcepoint…

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

Source evidenceVirusTotal 5 / 92 · OTX 4 references 5 sources

VirusTotal

5 / 92 engine detections

Buka laporan

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
5 / 92
OTX
4 community refs
Page captures
2

PhishDestroy threat report

Overview

linkedpaycheck.com is a phishing page that uses Telegram's name to pitch a payment service called Linkedpay. It is written for Russian-speaking users. PhishDestroy first detected it on 2026-09-27. On 2026-10-19 the site was still online and serving its content.

How the scam works

The page title reads "Linkedpay - карты и платежи в Telegram", which means "Linkedpay - cards and payments in Telegram". It sells the idea of a card and payment product built into the messenger. The title advertises a third-party payment brand, while our classification treats the site as Telegram impersonation phishing. Schemes like this usually borrow Telegram's trust to get visitors to sign in with their phone number, login code and cloud password, which hands over the account. Others ask for a deposit to "activate" or top up a card that never exists. Either way the victim can lose the Telegram account, its contacts and chats, and any money sent.

Evidence

VirusTotal shows 5 of 92 engines flagging the domain as of 2026-10-10. The vendors are alphaMountain.ai, Ermes, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. That is a low count, so many security products will still let the page load. Independent blocklists give stronger backing: the domain is listed by PhishDestroy, MetaMask and SEAL, which puts it on the radar of crypto-wallet defenders. It also appears in 4 AlienVault OTX threat pulses.

Infrastructure

The domain was registered on 2026-08-09, 49 days before PhishDestroy caught it. That suggests a site prepared in advance and then promoted to victims. Registration goes through Cloudflare, Inc., and the site sits behind Cloudflare's network, geolocated to Canada. That setup hides the real origin server from visitors and researchers.

What to do

If you entered a phone number, login code or password here, open Telegram's settings right away. Terminate every active session you don't recognize, then set or change your two-step verification cloud password. Warn your contacts, because hijacked accounts are often used to scam them next. If you paid to activate or fund a "Linkedpay" card, stop all further payments, keep your transaction details, and report the loss to your bank or payment provider and to the police. Security teams should block the domain at DNS and proxy level, add it to mail and messaging filters, and watch for lookalike domains that use the Linkedpay name.

Extracted from stored page analysis

Observed indicators

0 wallet · 1 Telegram

Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.

Telegram
https://t.me/linked_pay_botStored page reference

IoC extraction recorded 2026-09-28 04:00:09 UTC

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

Last checked

Tangkapan tersimpan · 2 captures

Domain details

Domain
URLScan verdict Analisis selesai score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Reputasi Edge-IP tidak dikaitkan dengan domain ini.
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomaindrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Cloudflare US(US)
PendaftaranDibuat 09/08/2026 (72d · New) — Expires 09/08/2027
Status HTTP200
Detail teknisProvenance & timestamps
Pertama Kali Terdeteksi27/09/2026
DOM Analysisanalyzed 09/10/2026score 95/1002 brand signals
IoC Extractionscanned 28/09/20260 wallet · 1 Telegram IoC
Submitted URLhttp://linkedpaycheck.com/
Favicon Hash
Observed page title
Linkedpay - карты и платежи в Telegram
Automated brand references
Apple Telegram
Sertifikat TLS
Diterbitkan oleh Google Trust Services / WE1 · stored validity ends in 76 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
104.21.65.148
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Reputasi Edge-IP tidak dikaitkan dengan domain ini.

Server nama 2

  • alexis.ns.cloudflare.com
  • eve.ns.cloudflare.com

Location describes the IP network.

Sertifikat TLS

Issuer
Google Trust Services / WE1
Valid from
2026-10-07 17:30:39
Valid until
2027-01-05 18:29:11
Validity
Within stored validity dates
Collection time
2026-10-11 07:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprinta98e8e7b07766ccd50709b3b8f46eb840ab0dc84361f955117aa240af6787905

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-21 01:56:34 UTC

Primary outcome Konten aktif reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Konten aktif Ordinary HTTP content served 90% 2026-10-21 01:56:34 UTC
RDAP registration Tidak diketahui
Observed timeline last reachable: 2026-10-21 01:56:34 UTC last content: 2026-10-21 01:56:34 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.
Teknologi · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Laporkan Domain Ini Kirimkan bukti & bantu lindungi orang lain

Analisis VirusTotal

5 / Vendor keamanan 92 menandai domain ini
View on VT
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
Ermes
Forcepoint ThreatSeeker
Gridinsoft
SOCRadar

Bukti Terarsip

Wayback Machine Snapshot
Cuplikan sejarah tersedia untuk tinjauan bukti
View Archive
Analisis Performa Situs

Google PageSpeed Insights — mobile performance audit of linkedpaycheck.com · checked Sep 27, 2026

92
Good
Performance
FCP
2.56s
First Contentful Paint
LCP
2.71s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.56s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Check for cloaking

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

linkedpaycheck.com
Hasil tersimpan
Cloaked / Filtered
Stored observation history21

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→live_content

    content_served

  2. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  3. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  4. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  5. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

Earlier observations 16
  1. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  2. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  3. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  4. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  5. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  6. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  7. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  8. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  9. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  10. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  11. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  12. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  13. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  14. Availability monitor · Recorded state

    Tidak diketahui→live_content

    content_served

  15. VirusTotal · Detection count

    0→2

  16. Availability monitor · First collection record

    Dapat dijangkau

Recorded activity

5 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    5/92 engine detections

    View source
  3. AlienVault OTX

    4 community references

    View source
  4. Added to PhishDestroy

    linkedpaycheck.com

    View source
  5. URLScan

    Page captured

    View source

Bukti & Laporan Eksternal

Analisis Mendalam
Help & reporting

Apakah Anda Terpengaruh oleh Situs Ini?

4 evidence signal groups linked 0 stored notification records Terakhir diketahui aktif

Listed domains receive at least one abuse report; this entry has no retained notification history.

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 linkedpaycheck.com)
  • 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/linkedpaycheck.com"
  title="PhishDestroy threat report for linkedpaycheck.com"
  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>