탐지를 보고하는 보안 엔진: 3. 일치를 보고하는 공개 차단 목록: 3. 극도의 주의를 기울이십시오 — 자격 증명이나 개인 정보를 입력하지 마십시오.
ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse-contact@publicdomainregistry.com.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
bnc4bnb.com is a fake token airdrop site that presented itself as a claim portal for a token called $BUILD. It targeted crypto wallet holders hoping to collect free tokens. PhishDestroy first detected it on 2026-09-17, just nine days after the domain was registered. The site has been offline since 2026-09-18, its content is blocked by the provider, and it was still down when last checked on 2026-10-19.
How the scam works
The page carried the title "$BUILD — Claim your tokens", the standard lure of a fake airdrop: a promise of free tokens that only need to be claimed. In schemes like this, the visitor is asked to connect a wallet and then sign a transaction or approval presented as the claim step. That signature actually gives the attacker permission to move the victim's tokens or NFTs, and the wallet is emptied shortly afterward. No real tokens are ever delivered, and on-chain transfers authorized this way cannot be reversed.
Evidence
On VirusTotal, 3 of 89 engines flagged the domain as of 2026-09-17: CRDF, Forcepoint ThreatSeeker and Kaspersky. That count is low, which is typical for a scam domain caught within days of launch. The classification is backed more strongly by wallet-security blocklists: besides PhishDestroy, the domain is listed by MetaMask, ScamSniffer and SEAL. It also appears in 3 AlienVault OTX threat pulses.
Infrastructure
The domain was registered on 2026-09-08 through PDR Ltd. d/b/a PublicDomainRegistry.com. It resolved to 104.21.18.151 on the Cloudflare, Inc. network, geolocated to CA, which means the true origin server sat behind Cloudflare's proxy. Its TLS certificate was issued by WE1.
What to do
If you connected a wallet to this site, use a token-approval checker to review and revoke any permissions granted around the time of your visit, and move remaining assets to a fresh wallet if you signed anything you did not fully understand. Anyone who entered a seed phrase or private key should treat that wallet as compromised and transfer funds immediately to a new one created on a clean device. Simply opening the page without connecting or signing is unlikely to have caused losses. Defenders should block the domain at DNS and web-proxy level and watch for lookalike claim pages using the same $BUILD lure.
등록 정보생성됨 2026년 9월 8일 (41d · New)—Expires 2027년 9월 8일
HTTP 상태403 Forbidden
Elapsed Since First Report31h
집계 기준
Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: 연결 가능 · 액세스가 제한됨.
각 보고서에 포함된 내용
저장된 발신 보고서 기록은 공급업체 평가, 등록 데이터, 호스팅 세부 정보, 분류 또는 스크린샷과 같이 당시 사용 가능한 증거를 참조할 수 있습니다. 이 페이지는 전달된 정확한 페이로드, 수신, 확인 또는 수신자의 작업을 추론하지 않습니다.
기술 세부 정보Provenance & timestamps
최초 발견2026년 9월 17일
DOM Analysisanalyzed 2026년 9월 17일score 93/1003 brand signals
IoC Extractionscanned 2026년 9월 17일1 wallet · 0 Telegram IoC
Submitted URLhttp://bnc4bnb.com/
Favicon Hash
사건 ID
Observed page title
$BUILD — Claim your tokens
Automated brand references
BNB ChainMetaMaskRabby
TLS 인증서
발급자 WE1
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
104.21.18.151
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP 평판은 이 도메인에 귀속되지 않습니다.
네임서버 2
agustin.ns.cloudflare.com
nola.ns.cloudflare.com
Location describes the IP network.
TLS 인증서
Issuer
WE1
Collection source
PhishDestroy collector
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Observed timelinelast reachable: 2026-09-17 23:03:11 UTCcurrent episode first observed: 2026-10-01 01:52:43 UTCobserved RIP window: 2026-09-17 23:03:11 UTC → 2026-10-01 01:52:43 UTC · 314.83hmidpoint estimate ≈ 2026-09-24 12:27:57 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.
기술 · 5 identified
H
HSTS
보안
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Blocklist hits included with submission:MetaMask, SEAL
PDF notice generated Notice text archived (639 chars)
Abuse notice text as sent to the provider
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 (RU):
Russian Criminal Code Article 159.6 (Computer Fraud)
Russian Criminal Code Article 272
Federal Law on Information
Russian law criminalizes computer fraud and unauthorized access to information systems.
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.
Template-based draft · optional AI wording assistance requires separate consent
AI 지원 초안 - 사고 세부정보는 AI 제공업체에서 처리됩니다. · 직접 검토하고 제출하세요.
After a phishing incident
피해자를 위한 권고 사항 및 조언
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.
모든 비밀번호 변경 — 이메일, 익스체인지 계정 등, 동일한 비밀번호를 사용하는 모든 것
2단계 인증 활성화 인증 앱(SMS 제외)을 사용합니다. SMS 기반 복구 기능을 비활성화하세요.
카드 동결 피싱 사이트에 은행 계좌 정보를 입력한 경우
보고서를 작성하기 위해 어떤 정보를 수집해야 할까요?
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.
정확한 날짜 및 시간 — 각 거래 내역 및 사기범과의 첫 접촉 시점
스크린샷 — 사기 웹사이트, 채팅 메시지, 이메일, 지갑 거래, 소셜 미디어
모든 URL 및 도메인 사기꾼이 사용한 (다음과 같은 것들을 포함하여 bnc4bnb.com)
커뮤니케이션 — 사기꾼이 사용한 이메일, 문자, 전화번호, 사용자 이름
비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
지역 경찰 — 비록 당장 조치를 취할 수는 없더라도 공식 기록을 남깁니다
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?
가짜 웹사이트 — 도메인을 약간만 변경한, 정식 사이트와 픽셀 단위로 완벽하게 일치하는 복제 사이트
pig butchering — Telegram·왓츠앱·데이트 앱을 통해 몇 주에 걸쳐 신뢰를 쌓은 뒤, 돈을 훔쳐갔다
회복 사기 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI를 이용한 사기 — 딥페이크, 자동화된 피싱, AI로 생성된 사이트 등으로 인해 사기 행각을 적발하기가 더 어려워지고 있다
앞으로 어떻게 하면 스스로를 지킬 수 있을까요?
공식 사이트 즐겨찾기 추가 — 이메일, DM 또는 광고에 포함된 링크는 절대 클릭하지 마세요
도메인 확인 — 확인하기 PhishDestroy 상호작용을 시작하기 전에 HTTPS, 맞춤법, 도메인 등록 기간을 확인하세요.
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.
(RU)
