Lompat ke laporan keamanan
Keamanan domain dan intelijen ancaman
btbt-007.com favicon

btbt-007.com

Registrar
NameCheap
Registered
03/09/2026
PhishDestroy assessment Kritis
Ketersediaan Konten tidak tersedia Konten tidak tersedia dalam observasi terbaru Teramati · HTTP probe
Deteksi Total Virus: 7/89 Label merek otomatis: Google Google Safe Browsing: threat flag recorded
OTX: 3 refs 08/09/2026
API
Domain ini telah ditandai sebagai berbahaya
Mesin keamanan melaporkan deteksi: 7. Berhati-hatilah — jangan memasukkan kredensial atau informasi pribadi.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Domain age
Ringkasan laporan

Peniruan Google: btbt-007.com — Konten tidak tersedia. Ringkasan bukti: VirusTotal 7/89 (alphaMountain.ai, CRDF, Google Safe Browsing, Kaspersky, Lionic)…

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

Source evidenceVirusTotal 7 / 89 · Google Safe Browsing: flagged · OTX 3 references 4 sources

VirusTotal

7 / 89 engine detections

Buka laporan

Google Safe Browsing

Threat flag recorded

Buka laporan

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

Analysis

Kritis
VirusTotal
7 / 89
OTX
3 community refs

PhishDestroy threat report

Overview

btbt-007.com is a phishing site that passed itself off as a legitimate crypto service to win visitors' trust. PhishDestroy first saw it on 2026-09-08, only five days after the domain was registered. The site went offline on 2026-09-16, and when we checked again on 2026-10-19 it was still dead with no active DNS. Copies of the same scheme often reappear under new, similar-looking domain names.

How the scam works

Impersonation pages copy the name, layout and tone of a service people already use. Victims arrive through ads, direct messages or search results and believe they are on the real platform. The page then asks them to log in, confirm an account, make a deposit, or enter wallet details. Whatever the victim types goes straight to the operators, who use it to take over accounts or move funds. The odd numbered domain name follows a common phishing pattern of spinning up disposable variants that can be swapped out as each one gets blocked.

Evidence

Google Safe Browsing labeled the site SOCIAL_ENGINEERING, its category for deceptive pages that trick users into giving up data or money. On VirusTotal, 7 of 89 engines flagged it as of 2026-09-17: alphaMountain.ai, CRDF, Google Safe Browsing, Kaspersky, Lionic, PhishFort and SOCRadar. That is a modest share of engines, but it includes Kaspersky and Google plus PhishFort, which focuses specifically on crypto phishing. The domain also appears in three AlienVault OTX threat pulses and on the PhishDestroy blocklist.

Infrastructure

The domain was registered through NameCheap, Inc. on 2026-09-03. It was live as a phishing page within days and stopped resolving by 2026-09-16. That gives the operation a lifespan of under two weeks, which fits throwaway infrastructure built to catch victims quickly before blocklists catch up.

What to do

If you entered a password on btbt-007.com, change it on the genuine service and on any other site where you used it. Then turn on app-based two-factor authentication and review your recent logins and sessions. If you sent money or made a deposit there, treat it as gone and ignore any follow-up messages promising recovery for a fee. If you typed a seed phrase or private key, move your remaining assets to a newly created wallet immediately. Defenders should block the domain and watch for similarly numbered lookalikes registered in the same period.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Domain details

Domain
Google Safe Browsing Ditandai Social engineering checked 17/09/2026
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomaindrainerfraudmonthlyphishdestroyphishingscam
Registrar NameCheap US(US)
PendaftaranDibuat 03/09/2026 (47d · New)
Waktu hingga pertama kali tidak tersedia 7 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 Terdeteksi08/09/2026

Network & certificates

Stored technical evidence

Network & DNS

Server nama 1

  • scott.ns.cloudflare.com

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 01:14:01 UTC
RDAP registration Tidak diketahui
Observed timeline last reachable: 2026-09-08 17:28:08 UTC current episode first observed: 2026-09-30 16:14:55 UTC observed RIP window: 2026-09-08 17:28:08 UTC → 2026-09-30 16:14:55 UTC · 526.78h midpoint estimate ≈ 2026-09-19 16:51:31 UTC · precision low · 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.
Laporkan Domain Ini Kirimkan bukti & bantu lindungi orang lain

Analisis VirusTotal

7 / Vendor keamanan 89 menandai domain ini
View on VT
Last analyzed First positive detection Previous stored snapshot: 7 detections
alphaMountain.ai
CRDF
Google Safe Browsing
Kaspersky
Lionic
PhishFort
SOCRadar
Registration & observation details8

Availability observations

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

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

Stored observation history13

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

    Tidak diketahui→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Tidak diketahui→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Tidak diketahui→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Tidak diketahui→dns_inactive

    dns_nxdomain

Earlier observations 8
  1. Availability monitor · Recorded state

    Tidak diketahui→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Tidak diketahui→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Tidak diketahui→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Tidak diketahui→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    Dapat dijangkau→Tidak tersedia

  7. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  8. Availability monitor · First collection record

    Dapat dijangkau

Recorded activity

4 entries
  1. AlienVault OTX

    3 community references

    View source
  2. Google Safe Browsing

    Threat flag recorded

    View source
  3. VirusTotal

    7/89 engine detections

    View source
  4. Added to PhishDestroy

    btbt-007.com

    View source

Intelijen komunitas

1 laporan komunitas

KategoriPHISHING

The PhishFort Detection System has flagged this as a domain threat, classified as null. Threat detected at 2026-09-08T10:49:30.314Z.

Check for cloaking

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

btbt-007.com

Bukti & Laporan Eksternal

Third-Party Detection — ChainAbuse
1 report filed for btbt-007.com · category: Phishing · source checked
Flagged by PhishFort Detection System on Sep 8, 2026 — automated submission, not a user testimony. Source: ChainAbuse (TRM Labs).
Analisis Mendalam
Help & reporting

Apakah Anda Terpengaruh oleh Situs Ini?

2 evidence signal groups linked 0 stored notification records Konten tidak tersedia

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 btbt-007.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/btbt-007.com"
  title="PhishDestroy threat report for btbt-007.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>