Stored evidence for v2-tronscan.net: VirusTotal recorded 10 detections among 91 scanners on 2026-09-27. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for v2-tronscan.net. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 10 detections among 91 scanners in the stored snapshot dated 2026-09-27. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-27 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
Source Context
MetaMask and SEAL are recorded as named external blocklist observations for v2-tronscan.net in the snapshot dated 2026-09-27. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains v2-tronscan.net as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
Reachability and Timeline
The record first observed v2-tronscan.net on 2026-09-27. The MetaMask and SEAL blocklist snapshot is dated 2026-09-27 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-09-03. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
Registration and Infrastructure
The source stores 188.114.96.1 as the observed address in this record. The registration date for v2-tronscan.net is recorded as 2026-09-03. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
Conclusion
The v2-tronscan.net record states that VirusTotal recorded 10 detections among 91 scanners on 2026-09-27. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-27. PhishDestroy remains a separate publisher catalogue entry in the stored record. The observed address field in this record contains 188.114.96.1. The supported conclusion is bounded to the exact stored observations for v2-tronscan.net. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to v2-tronscan.net during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain v2-tronscan.net as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to v2-tronscan.net. The stored record does not justify extending that rule to 188.114.96.1 or to other infrastructure records.
Extracted from stored page analysis
Observed indicators
19 wallet · 3 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeReachable but protectedreason: Cloudflare Challenge85% confidence
AttributionCloudflaremechanism: Challengesource: Current Http Probe
Evidence layersAvailability: Reachable but protectedContent: UnknownDNS: ResolvedRegistration: Unknown
Latest HTTP observationReachable but protectedCloudflare ChallengeCloudflareChallenge85%2026-10-19 01:55:39 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-19 01:55:39 UTC
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.
기술 · 2 identified
Cloudflare
CDN
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
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 및 도메인 사기꾼이 사용한 (다음과 같은 것들을 포함하여 v2-tronscan.net)
커뮤니케이션 — 사기꾼이 사용한 이메일, 문자, 전화번호, 사용자 이름
비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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.
(NL)
