VirusTotal
11 / 89 engine detections
Buka laporanbitfinex180.com: Peniruan 1inch, terdeteksi oleh PhishDestroy pada 2026-09-12. Risiko: kritis (100/100). Registrar: GMO Internet Group. Status: Konten tidak tersedia. Hosting: JT TELECOM INTERNATIONAL PTE.LTD. VirusTotal: 11/89 mesin menandainya. Tercantum di Spamhaus DBL. Jangan masukkan kredensial dan jangan hubungkan dompet.
“403 Forbidden”
Peniruan 1inch: bitfinex180.com — Konten tidak tersedia. Ringkasan bukti: VirusTotal 11/89 (alphaMountain.ai, BitDefender, Forcepoint ThreatSeeker, Fortinet…
Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.
11 / 89 engine detections
Buka laporanDBL_PHISH
4 community references
Buka laporanprovider verdict: clean
Buka laporanTidak ada penanda ancaman
Buka laporanTidak ada penanda berbahaya
Buka laporanHasil mencerminkan waktu pengumpulan setiap sumber. Nol deteksi tidak menjamin keamanan. Referensi OTX adalah publikasi komunitas.
PhishDestroy threat report
bitfinex180.com is a phishing domain built to pass as Bitfinex, the cryptocurrency exchange. The name pairs the real brand with a meaningless number, a common way to make a fake address look like an official mirror or promo site. It targets Bitfinex users and crypto traders. PhishDestroy first flagged it on 2026-09-12, and it has been offline since 2026-09-25, with its DNS still inactive as of 2026-10-19.
Exchange impersonation pages copy a brand's look to collect what protects an account. Victims are typically asked for their login email and password, and often a 2FA code, which the operators can replay right away to log in and withdraw funds. Some variants instead push fake deposit or wallet-verification steps that send crypto straight to the scammers. When last served, the page returned a "403 Forbidden" title rather than a Bitfinex-styled page. We classify it as impersonation phishing based on the domain name and independent detections.
Eleven of 89 VirusTotal engines flagged the domain as of 2026-09-23. The flagging vendors include alphaMountain.ai, BitDefender, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Kaspersky and Netcraft. That is broad agreement among separate security vendors, not a single outlier. Spamhaus lists the domain in its DBL under the phishing category. It also appears in four AlienVault OTX threat pulses and on the PhishDestroy blocklist.
The domain was registered on 2026-09-09 through GMO Internet Group (Onamae.com), only three days before PhishDestroy detected it. That short gap fits a domain bought specifically for a campaign. It was hosted on the JT TELECOM INTERNATIONAL network in Japan. It went dark roughly two weeks after detection, a typical lifespan for a throwaway phishing domain.
If you entered your Bitfinex login on this site, change your password from the official app or a bookmarked address, then reset two-factor authentication and end all active sessions. Check your account for API keys, withdrawal addresses or whitelist changes you did not make, and contact Bitfinex support if anything looks wrong. If you sent crypto as a "deposit" or verification payment, treat it as lost and report it. Do not pay anyone who promises to recover it. Defenders should block the domain and look for related bitfinex-plus-number lookalikes in DNS and proxy logs.
Pengamatan halaman, jaringan, dan pemindai yang tersimpan, dikelompokkan berdasarkan sumber dan waktu pengamatan.
Teramati: · Retrieved:
| Uuid | 01a0ba87-26bb-73d9-b79f-54e2700adc97 |
|---|---|
| Final url | https://bitfinex180.com/wap/ |
| Status | 200 |
| Dialihkan | same-domain |
| Redirects | [
{
"to": "https://bitfinex177.com/",
"from": "https://bitfinex180.com/",
"status": 302
},
{
"to": "https://bitfinex180.com:28520/",
"from": "https://bitfinex177.com/"
},
{
"to": "https://bitfinex180.com/wap/",
"from": "https://bitfinex180.com:28520/",
"status": 302
}
] |
| Ip | 172.81.98.56 |
| Contacted domains | [
"bitfinex177.com",
"cdnjs.cloudflare.com",
"static.cloudflareinsights.com"
] |
| Contacted IP addresses | [
"104.17.24.14",
"2606:4700::6810:4f49",
"172.67.204.230",
"172.81.98.56"
] |
| Asns | [
"13335",
"137535"
] |
| Countries | [
"US",
"JP"
] |
| Document hash | 1e4b7c8150bff5f21bdb39e3879dab22b9d59d949780b752886c5e11af38d5d1 |
| Script hashes | [
"ac17ebfd2f332f03125ede8bc97ef3f81d70f54150b66597e5f42c7eef57829f",
"d84d20b32bf61cfec5f536639e52a6c21925bb7b08ed7485ad6aa71502b317bf",
"1b7efeb048f7db7f21ea0cd7397d5e5bbbffa031915001a386b4e18f0866d6d9",
"24be5cc05161f5c72faf5594ba55a0fe0a94e1ad61786f25208cc663bc82f7d1",
"878daef856219c15d7ea4aee2db7806fb60178935bdb9296c98379096b996339",
"6e8acf0ae4a999213d22dd787ddbe45bedc09766323544c75d6825bdb8c62e3c",
"5d206a9e8147c77248438214e185974a70f8214b30f353f12bc33192d24e1d93",
"a3e80b4ab4f22d77f9d9348d3b668455e1e7a10684c816c951a1956b0f8e5473",
"91c11cf709d7994441b02ada4dfda08c7bf37558da62bbe52e3db0a2744598f3",
"3542e26499bfbd6f84fa973b3923a52ae61fee24b092bbadec76314ab282c12c"
] |
| Globals | [
"webpackChunkexchange",
"clearImmediate",
"setImmediate",
"eventBus",
"_PageAccelerator",
"pageAccelerator"
] |
| Cookie | [
"server_session_0eb1b4d8"
] |
| Storage keys | [
"@@",
"lang",
"vuex",
"categoryNum"
] |
| Tls | {
"san": [
"*.bitfinex177.com",
"bitfinex177.com"
],
"cipher": "AES_128_GCM",
"issuer": "YE2",
"subject": "bitfinex177.com",
"protocol": "QUIC",
"valid_to": "2026-12-18T11:49:51Z",
"valid_from": "2026-09-19T11:49:52Z"
} |
| Usia domain (hari) | 9 |
| Apex age days | 9 |
| Tls age days | 0 |
| Masa berlaku TLS (hari) | 89 |
| Requests | 234 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 100,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "cloudflare",
"content-type": "text/html; charset=utf-8"
} |
Teramati: · Retrieved:
| Uuid | 0a335e32-f433-4f45-9c91-51fbf56ddaaf |
|---|---|
| Final url | https://bitfinex177.com/ |
| Status | 200 |
| Dialihkan | off-domain |
| History | [
{
"url": "http://bitfinex180.com/",
"status": 307
},
{
"url": "https://bitfinex180.com/",
"status": 302
},
{
"url": "https://bitfinex177.com/",
"status": 200
}
] |
| DOM structure hash | e385b634ec2a34081d6136f9ea71b4f27a23282b22b5ad506b44b47ece1a52d4 |
| Document hash | 1e4b7c8150bff5f21bdb39e3879dab22b9d59d949780b752886c5e11af38d5d1 |
| Phishing v2 | [
"phishing"
] |
| Risiko domain | [
"Newly Seen Domains",
"Security Risks"
] |
| Radar rank | {
"bucket": ">200000"
} |
| Catatan DNS | [
{
"name": "bitfinex177.com",
"type": "A",
"value": "172.67.204.230"
},
{
"name": "bitfinex177.com",
"type": "A",
"value": "104.21.69.52"
},
{
"name": "bitfinex177.com",
"type": "AAAA",
"value": "2606:4700:3033::ac43:cce6"
},
{
"name": "bitfinex177.com",
"type": "AAAA",
"value": "2606:4700:3037::6815:4534"
}
] |
| DNSSEC valid | false |
| Ip | 172.67.204.230 |
| Catatan pendaftaran | {
"registrar": "GMO Internet Group, Inc. d/b/a Onamae.com",
"created": "2026-09-19T12:41:52Z",
"updated": "2026-09-19T12:43:35Z",
"expires": "2027-09-19T12:41:52Z",
"nameservers": [
"candy.ns.cloudflare.com",
"lars.ns.cloudflare.com"
]
} |
Teramati: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 46,
"malicious": 11,
"suspicious": 1,
"undetected": 34
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"ESET": "suspicious",
"G-Data": "phishing",
"Lionic": "phishing",
"Sophos": "malware",
"Fortinet": "phishing",
"SOCRadar": "phishing",
"Kaspersky": "phishing",
"PhishFort": "phishing",
"BitDefender": "phishing",
"alphaMountain.ai": "phishing",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Tags | [
"dga"
] |
| Categories | {
"alphaMountain.ai": "Phishing, Newly Registered (alphaMountain.ai)"
} |
| Registrar | GMO Internet Group, Inc. d/b/a Onamae.com |
| Dibuat | 2026-09-09T12:48:51Z |
| Expires | 2027-09-09T12:48:51Z |
| Updated | 2026-09-09T12:49:02Z |
| Pertama terlihat | 2026-09-10T08:18:27Z |
| Catatan DNS | [
{
"ttl": 21600,
"type": "NS",
"value": "a.share-dns.com"
},
{
"ttl": 600,
"type": "A",
"value": "172.81.98.56"
},
{
"ttl": 600,
"type": "SOA",
"rname": "master.share-dns.com",
"value": "a.share-dns.com"
},
{
"ttl": 21600,
"type": "NS",
"value": "b.share-dns.net"
}
] |
| Dns at | 2026-09-23T09:45:29Z |
| Jarm | 40d40d40d00040d00042d42d000000e1ea2a807a629b496b664cf07ad7c08d |
| Certificate | {
"san": [
"bitfinex137.com",
"bitfinex167.com",
"bitfinex180.com",
"bitfinex188.com"
],
"issuer": "Let's Encrypt / YE2",
"serial": "6d7671060e60cdcf03a75f8c191b55ea5f8",
"sha256": "8b1127919fd09b061732dc3cf2c1d544c009ebcea2026539ab5f275a56508171",
"subject": "bitfinex180.com",
"valid_to": "2026-12-18T15:43:12Z",
"valid_from": "2026-09-19T15:43:13Z"
} |
| Catatan pendaftaran | {
"registrar": "GMO Internet Group, Inc. d/b/a Onamae.com",
"registrar_iana_id": "49",
"registrar_url": "https://internet.gmo/",
"created": "2026-09-09T12:48:51Z",
"updated": "2026-09-09T12:49:02Z",
"expires": "2027-09-09T12:48:51Z",
"status": [
"clientTransferProhibited"
],
"nameservers": [
"a11.share-dns.com",
"b11.share-dns.net"
],
"dnssec": "unsigned"
} |
| Registry data | {
"status": [
"client transfer prohibited",
"client update prohibited"
],
"events": {
"expiration": "2027-09-08T15:00:00Z",
"last changed": "2026-09-09T12:59:05Z",
"registration": "2026-09-09T03:48:51Z",
"registrar expiration": "2027-09-08T15:00:00Z",
"last update of RDAP database": "2026-10-08T07:07:21Z"
}
} |
Tidak. PhishDestroy mengklasifikasikan bitfinex180.com sebagai Peniruan 1inch (risiko: kritis, 100/100); pertama kali terdeteksi pada 2026-09-12. VirusTotal: 11/89 mesin menandainya. Tercantum di Spamhaus DBL. Anggap situs ini tidak aman.
Tidak. Jangan hubungkan dompet, menandatangani pesan, atau menyetujui token di bitfinex180.com. Situs phishing meminta persetujuan (approve, setApprovalForAll, Permit2) yang memungkinkan operator memindahkan aset Anda, dan transaksi yang sudah dikonfirmasi tidak dapat dibatalkan.
Ganti setiap kata sandi yang Anda masukkan di sana dan aktifkan autentikasi dua faktor. Jika Anda menghubungkan dompet atau menandatangani sesuatu, cabut persetujuannya dan pindahkan dana yang tersisa ke dompet baru; jangan pernah membagikan frasa pemulihan. Bantuan langkah demi langkah: panduan darurat.
Reputasi Edge-IP tidak dikaitkan dengan domain ini.
b11.share-dns.netLokasi menggambarkan jaringan IP.
029089892575ced79820836eb2b1ba44863d11b160764f5c7065333494c401d7bitfinex181.combitfinex182.combitfinex183.combitfinex184.combitfinex185.combitfinex186.combitfinex187.combitfinex188.combitfinex189.comMetadata sertifikat yang disimpan. Tanggal sertifikat tanpa zona waktu ditampilkan sebagaimana disimpan. Enkripsi transport tidak membuktikan bahwa situs tersebut tepercaya.
Google PageSpeed Insights — audit performa seluler untuk bitfinex180.com · checked Sep 20, 2026
Waktu perkiraan menggambarkan rentang pengamatan. Waktu ini tidak membuktikan tindakan registrar atau saat pasti situs menjadi tidak tersedia.
Perubahan bertanggal yang disimpan oleh pemantau dan kolektor sumber. Pengamatan terbaru ditampilkan lebih dulu; status sumber bukan bukti bahwa situs telah diturunkan.
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
Tidak diketahui→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
Dapat dijangkau→Tidak tersedia
5→3
Dapat dijangkau
Tidak ada penanda ancaman
Lihat sumber11/89 engine detections
Lihat sumber4 community references
Lihat sumberbitfinex180.com
Lihat sumber1 laporan komunitas
KategoriIMPERSONATION
Brand abuse: impersonation, impersonating Bitfinex
Bandingkan apa yang diterima browser dan crawler, serta periksa perutean trafik Keitaro.
bitfinex180.com
Domain dalam daftar menerima setidaknya satu laporan penyalahgunaan; entri ini tidak memiliki riwayat notifikasi yang tersimpan.
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.
Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.
Template-based draft · optional AI wording assistance requires separate consent
Pilih langkah yang sesuai dengan informasi yang Anda bagikan. Simpan salinan laporan ini bersama catatan Anda sendiri.
Berhenti menggunakan situs yang mencurigakan. Buka layanan yang asli melalui aplikasi resminya atau alamat yang sudah Anda percayai.
Simpan email, tanda terima, pesan, dan tangkapan layar asli di tempat yang aman. Kronologi faktual membantu otoritas penerima memahami apa yang terjadi. IC3 evidence guidance ↗
bitfinex180.com)Meskipun kamu belum mengetahui semua detailnya — tetap saja ajukan laporan. Informasi yang tidak lengkap tetap dapat membantu penyelidikan.
Laporan tidak menjamin dana akan kembali atau kasus akan diselidiki, tetapi data transaksi yang akurat dan segera disampaikan dapat membantu pihak berwenang dan penyedia layanan melacak insiden tersebut.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Analisis ancaman menggunakan daftar blokir yang disimpan, WHOIS, DNS, dan bukti pemindaian publik
Pindai SekarangLaporkan domain yang mencurigakan ke basis data ancaman kami — lindungi komunitas
LaporanLaporan phishing terbaru dan perubahan ketersediaan yang diamati
PantauPantau ancaman secara langsung atau ajukan keberatan terhadap daftar ini jika Anda yakin ini merupakan false positive
Laporan ini menggabungkan tangkapan halaman yang disimpan, catatan pendaftaran dan jaringan, hasil pemindai, serta riwayat pelaporan PhishDestroy. Setiap sumber menyimpan tanggal pengamatannya sendiri. Buka laporan sumber untuk memeriksa hasil aslinya.
Analisis berbantuan AI ditulis pada . Analisis ini menggambarkan bukti yang tersedia saat itu; hasil pemeriksaan sumber berikutnya dapat berbeda.
Tangkapan mendokumentasikan apa yang ditampilkan. Hasil pemindai mencatat penilaian penyedia tersebut pada saat pemeriksaan. Baik sertifikat yang valid maupun hasil tanpa deteksi tidak menjamin keamanan.