VirusTotal
4 / 92 engine detections
Raporu aç“BingNC”
MetaMask taklidi: bingnc.net — İçerik kullanılamıyor. Kanıt özeti: VirusTotal 4/92 (alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar); 2…
Özgün adli kaydı korumak için aşağıdaki ayrıntılı PhishDestroy AI analizi İngilizce bırakılmıştır.
4 / 92 engine detections
Raporu açScan report
Raporu aç4 community references
Raporu açprovider verdict: clean
Raporu açNo threat flag
Raporu açNo malicious flag
Raporu açResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
bingnc.net ran a page titled "BingNC", a made-up brand meant to pass as a legitimate crypto service. Its listing by MetaMask and SEAL points to crypto holders and wallet users as the intended victims. PhishDestroy first detected it on 2026-09-27. The site has been offline since 2026-10-14 and was still unreachable on 2026-10-19.
Impersonation pages like BingNC copy the name and look of a familiar trading or wallet service closely enough that a hurried visitor trusts them. The visitor is then pushed to log in, type a recovery phrase, deposit funds or connect a wallet. Each of those hands control to the operators. Typed credentials and seed phrases let them empty accounts directly, and a wallet connection can trick the victim into signing an approval that lets the attacker move tokens. Money sent as a deposit simply never comes back.
On 2026-10-10, 4 of 92 VirusTotal engines flagged the domain: alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. That count is low, but the crypto-specific blocklists matter more here. MetaMask and SEAL both list bingnc.net alongside PhishDestroy, so wallet users relying on those protections would have been warned. The domain also appears in 4 AlienVault OTX threat pulses, which means other researchers tracked it independently.
The domain was registered on 2026-06-17 through Hosting Concepts B.V. d/b/a Registrar.eu, about three months before PhishDestroy caught it. That gap suggests the domain was set up well in advance rather than spun up for a single burst. It was hosted on a US address, 178.98.16.82. Once flagged across several blocklists, the site went down within about three weeks.
If you entered a password or 2FA code on BingNC, change it at the real service you thought you were using and turn on app-based two-factor authentication. If you typed a recovery phrase, treat that wallet as lost: create a new wallet and move any remaining assets to it immediately. If you connected a wallet, review and revoke any token approvals you granted while on the site. Do not pay anyone who offers to recover deposits, because that is a common follow-up scam. Defenders should block the domain and its hosting IP and check proxy logs for visits from 2026-09-27 onward.
Last checked
laura.ns.cloudflare.comrommy.ns.cloudflare.comLocation describes the IP network.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of bingnc.net · checked Sep 27, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Erişilebilir→Mevcut değil
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
0→1
Erişilebilir
No threat flag
View source4/92 engine detections
View source4 community references
View sourcePD-20260927-C5320D
bingnc.net
View sourcePage captured
View source79 kayıtlı benzer alan adı
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
bingnc.net
PD-20260927-C5320D Recipient: abuse@registrar.eu Policy Violations: Illegal Activities: Active phishing operation targeting victims Fraud & Deception: Impersonation of legitimate services Identity Theft: Collection of credentials under false pretenses Applicable Laws (US): 18 U.S.C. § 1343 - Wire Fraud 18 U.S.C. § 1030 - Computer Fraud and Abuse Act (CFAA) 15 U.S.C. § 45 - FTC Act (Deceptive Practices) Federal laws prohibit wire fraud, computer fraud, and deceptive business practices. Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
Hesap kimlik bilgilerini, kişisel bilgileri veya ödeme bilgilerini girdiyseniz ya da bu alan adından bir dosya indirdiyseniz hemen harekete geçin. Aşağıda olayı bildirmenize ve kendinizi korumanıza yardımcı olacak kaynaklar bulunmaktadır.
resmi siber suç iletişim bilgileri veya şikayet taslağı oluştur → almak için ülkenizi seçin.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
bingnc.net)Tüm ayrıntıları bilmeseniz bile — yine de şikayette bulun. Kısmi bilgiler de soruşturmalara yardımcı olmaktadır.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Saklanan engelleme listesi, WHOIS, DNS ve genel tarama kanıtlarını kullanarak tehdit analizi
Şimdi TaraŞüpheli alan adlarını tehdit veritabanımıza bildirin — topluluğu koruyun
BildirSon kimlik avı raporları ve gözlemlenen kullanılabilirlik değişiklikleri
İzleCanlı tehditleri izleyin veya bunun yanlış bir uyarı olduğunu düşünüyorsanız bu kayda itiraz edin
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.