VirusTotal
14 / 91 engine detections
보고서 열기“Bittensor”
bittensor-dapp.io — 마지막으로 알려진 활성 (HTTP 200). 브랜드 사칭: Tensor; 사기 유형: Impersonation. 증거 요약: VirusTotal 14/91 (alphaMountain.ai, BitDefender, CRDF, CyRadar, Forcepoint ThreatSeeker); 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 100/100. 등록기관: Name.com.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
14 / 91 engine detections
보고서 열기Suspicious
보고서 열기3 community references
보고서 열기No threat flag
보고서 열기No malicious flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
bittensor-dapp.io is an impersonation phishing page that PhishDestroy classifies as imitating Tensor, aimed at crypto users who expect to interact with a legitimate dapp. The page title reads "Bittensor", while our classification names Tensor as the impersonated brand. PhishDestroy first detected the domain on 2026-10-03. As of 2026-10-19 the site was still online and serving its content, so it remains a live risk.
The "-dapp" domain and the "Bittensor" title are meant to look like the official app interface of a well-known crypto project. Pages like this typically ask the visitor to connect a wallet to claim, stake or verify something. They then present a signature or approval request that hands the attacker control over tokens or NFTs. Some variants instead ask for a seed phrase under the pretext of syncing or restoring the wallet. Either way, the victim can lose whatever the wallet holds, and on-chain transfers cannot be reversed.
On 2026-10-06, 14 of 91 VirusTotal engines flagged the domain, including BitDefender, Fortinet, Forcepoint ThreatSeeker, G-Data, alphaMountain.ai, CRDF, CyRadar and Gridinsoft. That is a meaningful detection level for a site only about a week old. The domain is also on the MetaMask and SEAL blocklists alongside PhishDestroy's own, so wallet users with those protections may see a warning. Three AlienVault OTX pulses reference it, showing other researchers have tracked it independently.
The domain was registered through Name.com, Inc. on 2026-09-29, just four days before PhishDestroy caught it. That short gap fits a throwaway domain set up for a fast campaign. The site runs on Amazon cloud infrastructure in Germany, which is easy to provision and replace. It uses a free Let's Encrypt certificate, so the browser padlock says nothing about whether the site is legitimate.
If you connected a wallet to bittensor-dapp.io and signed anything, revoke token and NFT approvals immediately with a trusted approval-management tool. Move remaining assets to a fresh wallet. If you typed in a seed phrase, treat that wallet as fully compromised and transfer funds out before the attacker does. Only reach the Bittensor or Tensor apps through addresses you have verified yourself, never through links in ads, DMs or search results. Defenders should block the domain at DNS and proxy level and report it to the hosting provider and registrar, since it was still live on 2026-10-19.
Last checked
Edge-IP 평판은 이 도메인에 귀속되지 않습니다.
dns1.p06.nsone.netdns2.p06.nsone.netdns3.p06.nsone.netdns4.p06.nsone.netLocation describes the IP network.
7a8fcd9797052c48541583618454e6ec22f9348ddf12eeb5549a4db04a403b44Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
alive_content: raw=ok; http=200; via=https_proxy; server=Netlify
bittensor-dapp.io
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
접속 가능
No threat flag
View source14/91 engine detections
View source3 community references
View sourcePage captured
View sourcebittensor-dapp.io
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
계정 자격 증명, 개인 정보 또는 결제 정보를 입력했거나 이 도메인에서 파일을 다운로드한 경우 즉시 조치를 취하세요. 다음은 사건을 신고하고 자신을 보호하는 데 도움이 되는 리소스입니다.
공식 사이버 범죄 연락처 또는 불만사항 초안 작성 →를 받으려면 국가를 선택하세요.
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 ↗
bittensor-dapp.io)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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
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.