VirusTotal
8 / 89 engine detections
レポートを開く“EasyWeb Login - TD Canada Trust”
認証情報フィッシング: nl2.hypervpn.cc — コンテンツが利用できません. 証拠の概要: VirusTotal 8/89 (CRDF, Forcepoint ThreatSeeker, Fortinet, Google Safe Browsing, Gridinsoft); URLQuery 3…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
8 / 89 engine detections
レポートを開く3 threat-system alerts
レポートを開く15/100
レポートを開くThreat flag recorded
レポートを開く悪意あり
レポートを開くno community references
レポートを開くprovider verdict: clean
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| YARAhub by abuse.ch | nl2.hypervpn.cc/signin/login.html |
malware | Detects file containing Telegram Bot API |
| OpenDNS | nl2.hypervpn.cc |
phishing | Phishing Block |
| DNS4EU | nl2.hypervpn.cc |
malicious | Sinkholed |
PhishDestroy threat report
nl2.hypervpn.cc is a credential phishing page impersonating TD Bank. It served a page titled "EasyWeb Login - TD Canada Trust", a copy of the online banking sign-in used by TD's Canadian customers. PhishDestroy first saw it on 2026-09-11. The site has been offline since 2026-09-14, and its DNS was still inactive when last checked on 2026-10-19.
Victims usually reach a page like this through a text message or email warning of a locked account, a suspicious payment or a required security check. The fake EasyWeb form asks for the card number or username and password, and kits of this kind often follow up with security questions or a one-time passcode prompt. Whatever is typed goes to the operators, who can log into the real account, move money or reset access before the customer notices. The hostname belongs to a domain styled as a VPN service and has no connection to TD, so the address bar is the clearest warning sign.
Eight of 89 VirusTotal engines flagged the site as of 2026-09-15: CRDF, Forcepoint ThreatSeeker, Fortinet, Google Safe Browsing, Gridinsoft, SafeToOpen, SOCRadar and Webroot. That is a modest count, but it includes Google Safe Browsing, which listed the page under SOCIAL_ENGINEERING and triggers warnings in mainstream browsers. urlscan.io returned a malicious verdict and identified the TD Bank branding on the page. PhishDestroy lists the domain on its blocklist.
The parent domain was registered through NAMECHEAP INC on 2025-12-21, about nine months before the phishing page appeared. That gap suggests a domain held in reserve rather than one registered for this single page. The page was hosted at 107.189.18.119 on the RouterHosting LLC network, a US provider, with the server located in the Netherlands. It went dark three days after PhishDestroy first detected it.
If you entered your EasyWeb credentials here, change your TD password immediately from the official app or by typing the bank's address yourself. Then call TD using the number on the back of your card so they can lock the account and review recent transactions. Change any other account that used the same password, turn on two-step verification, and do not share a one-time code with anyone who calls or texts. Defenders should block the domain and IP at the mail and web gateways and search logs for clicks or form submissions to this host around 2026-09-11 to 2026-09-14.
dns1.registrar-servers.comdns2.registrar-servers.comLocation describes the IP network.
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.
nl2.hypervpn.cc
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
到達可能→利用不可
7→8
8→7
No flag recorded→Flag recorded
到達可能
Threat flag recorded
View source8/89 engine detections
View sourcePD-20260911-3E5608
nl2.hypervpn.cc
View sourcePage captured
View sourcePD-20260911-3E5608 Recipient: abuse@namecheap.com Registrar: Namecheap Inc (United States) Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
nl2.hypervpn.cc)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.