跳转到安全报告
域安全和威胁情报
nl2.hypervpn.cc favicon

nl2.hypervpn.cc

“EasyWeb Login - TD Canada Trust”

注册商
Namecheap
Resolved IP
107.189.18.119
Registered
2025年12月21日
PhishDestroy assessment 关键
可用性 内容不可用 最新观察中的内容不可用 观察到 · HTTP probe
病毒检测总数:8/89 URLQuery threat systems: 3 alerts 自动品牌标签:Tdbank Google Safe Browsing: threat flag recorded
2026年9月11日 1 Report Sent
API
该域名已被标记为恶意域名
安全引擎报告检测:8。 请格外小心——不要输入凭据或个人信息。
VirusTotal
engine detections
Google Safe Browsing
URLQuery
threat alerts
Page captures
open gallery
Domain age
Reports sent
view timeline
报告概览

凭据钓鱼: nl2.hypervpn.cc — 内容不可用. 证据摘要: VirusTotal 8/89 (CRDF, Forcepoint ThreatSeeker, Fortinet, Google Safe Browsing, Gridinsoft); URLQuery 3 alerts; URLScan…

为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。

Source evidenceVirusTotal 8 / 89 · Google Safe Browsing: flagged 7 sources

VirusTotal

8 / 89 engine detections

打开报告

URLQuery

3 threat-system alerts

打开报告

Google Safe Browsing

Threat flag recorded

打开报告

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

网络安全情报
Threat Detection Systems 3 alerts
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

Analysis

关键
VirusTotal
8 / 89
Page captures
4

PhishDestroy threat report

Overview

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.

How the scam works

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.

Evidence

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.

Infrastructure

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.

What to do

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.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

已保存的截图 · 4 captures

Domain details

域名
URLScan verdict 恶意 score 100 Phishing brand: Tdbank report ↗
Google Safe Browsing 已标记 Social engineering checked 2026年9月15日
IP 信誉 abuse score 0/100 0 reports checked 2026年9月11日
Registrar (base domain) Namecheap US(US)
滥用举报联系方式abuse-reports@cloudzy.com, abuse@namecheap.com
ICANN 注册管理机构ICANN Lookup (RDAP) →
Registration (base domain)hypervpn.cc · 创建 2025年12月21日 (303d) — Expires 2026年12月21日
首次不可用所需时间 3 days
统计口径 从第一个存储的滥用报告到第一次观察到内容不可用所经过的时间。这并不能确定原因。
每份报告包含哪些内容 存储的传出报告记录可以参考当时可用的证据,例如供应商判决、注册数据、托管详细信息、分类或屏幕截图。此页面无法推断收件人交付、接收、确认或操作的确切有效负载。
技术详情Provenance & timestamps
首次发现2026年9月11日
DOM Analysisanalyzed 2026年9月11日score 88/1001 brand signal
Submitted URLhttp://nl2.hypervpn.cc/signin/login.html
Favicon Hash
案件 ID
Observed page title
EasyWeb Login - TD Canada Trust
Automated brand references
Tdbank

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
107.189.18.119
Network ASN
AS14956
Organization
RouterHosting LLC
Observed location
Zaandam, NL
Server header
Apache/2.4.58 (Ubuntu)

域名服务器 2

  • dns1.registrar-servers.com
  • dns2.registrar-servers.com

Location describes the IP network.

Latest Classified Outcome 2026-10-20 08:21:37 UTC

Primary outcome DNS 非活动 reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation 未知 Probe Inconclusive 20% 2026-10-19 01:14:01 UTC
RDAP registration 未知
Observed timeline last reachable: 2026-09-13 22:54:31 UTC current episode first observed: 2026-09-30 16:14:55 UTC observed RIP window: 2026-09-13 22:54:31 UTC → 2026-09-30 16:14:55 UTC · 401.34h midpoint estimate ≈ 2026-09-22 07:34:43 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.
举报此域名 提交证据,帮助保护他人

VirusTotal 分析

8 / 89 安全供应商标记了该域
View on VT
Last analyzed First positive detection Previous stored snapshot: 8 detections
CRDF
Forcepoint ThreatSeeker
Fortinet
Google Safe Browsing
Gridinsoft
SafeToOpen
SOCRadar
Webroot
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
401.34
Estimate basis
Bounded by observations
Estimate precision
Low

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

nl2.hypervpn.cc
已保存的结果
无法访问
Stored observation history15

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

Earlier observations 10
  1. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    可访问→不可用

  7. VirusTotal · Detection count

    7→8

  8. VirusTotal · Detection count

    8→7

  9. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  10. Availability monitor · First collection record

    可访问

Recorded activity

5 entries
  1. Google Safe Browsing

    Threat flag recorded

    View source
  2. VirusTotal

    8/89 engine detections

    View source
  3. Abuse report sent

    PD-20260911-3E5608

    abuse@namecheap.com
  4. Added to PhishDestroy

    nl2.hypervpn.cc

    View source
  5. URLScan

    Page captured

    View source

证据与外部报告

已提交证据快照
Sent: Ledger records: 1 Case ID: PD-20260911-3E5608 Recipient: abuse@namecheap.com
PDF notice generated Notice text archived (289 chars)
Abuse notice text as sent to the provider
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
深度分析
Help & reporting

您是否受到本网站的影响?

6 evidence signal groups linked 1 stored notification records 内容不可用
If credentials were compromised, report immediately. Do not engage with recovery scammers.

如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。

Official reporting routes

警惕“数据恢复”诈骗! 犯罪分子可能会冒充调查员、律师或追债员再次联系受害者。 请勿支付预付费用或共享凭证。 了解有关康复欺诈的更多信息 →

向当地主管部门报告

选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。

97个国家目录

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.

  • 更改所有密码 — 电子邮件、Exchange 账户,以及任何使用同一密码的账户
  • 启用双因素认证 使用身份验证器应用(而非短信)。禁用基于短信的恢复功能
  • 冻结卡片 如果您在钓鱼网站上输入了银行信息

我应该为报告收集哪些信息?

联邦调查局(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.
  • 确切日期和时间 — 每笔交易的详情以及与诈骗者的首次接触
  • 屏幕截图 — 诈骗网站、聊天消息、电子邮件、钱包交易、社交媒体
  • 所有网址和域名 诈骗者使用的(包括 nl2.hypervpn.cc)
  • 通信 — 诈骗者使用的电子邮件、短信、电话号码、用户名

即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。

我应该向哪里举报这起诈骗?

  • 联邦调查局(FBI)IC3 — 互联网犯罪投诉中心(美国联邦举报渠道)
  • 欧洲刑警组织 — 欧洲网络犯罪报告(欧盟)
  • 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?

  • 虚假网站 — 与正规网站完全一致的克隆网站,仅域名略有改动
  • 猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任,随后钱被骗走
  • 退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • 利用人工智能实施的诈骗 — 深度伪造、自动化网络钓鱼以及人工智能生成的网站,使得欺诈行为更难被察觉

将来我该如何保护自己?

  • 将官方网站添加到书签 — 切勿点击来自电子邮件、私信或广告中的链接
  • 验证域名 — 查看 PhishDestroy 在进行互动之前,请检查HTTPS、拼写和域名注册时间。
  • “好得令人难以置信”=骗局 — 保证收益、名人代言、紧迫的截止日期

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

随时掌握最新信息,确保安全

请实时监控威胁,或者如果您认为这是误报,请对该条目提出异议

实时威胁动态 对该列表提出异议
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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

嵌入此报告

在您的网站或博客上分享此威胁情报

embed.html
<iframe
  src="https://phishdestroy.io/zh/embed/domain/nl2.hypervpn.cc"
  title="PhishDestroy threat report for nl2.hypervpn.cc"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>