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@key-systems.net.
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.
laso.cx is a phishing page that presents itself as Laso Finance and carries the title "Laso Finance | Home" to pass as the brand's front page. It targets crypto users who expect to reach the real service. PhishDestroy first flagged it on 2026-09-11. As of 2026-10-19 the site was still online and serving its content, so anyone who finds it through a link or search can still land on it.
How the scam works
Impersonation pages like this copy a brand's homepage closely enough that a visitor assumes they are on the real site, then lead them to the step that matters to the attacker. urlscan.io matched the page to a generic crypto template, and wallet-focused blocklists have listed the domain. Both point to the usual crypto play. The visitor is asked to connect a wallet and sign transactions or approvals, or to enter a seed phrase or login details. Any of these can hand over control of funds, and once assets leave the wallet the transfer cannot be reversed.
Evidence
On 2026-09-21, 13 of 89 VirusTotal engines flagged the domain, including alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data and Gridinsoft. urlscan.io returned a malicious verdict. Spamhaus lists it in its DBL under the phishing category, which affects email and DNS filtering widely. MetaMask and SEAL have both blocklisted it alongside PhishDestroy, and it appears in 4 AlienVault OTX threat pulses.
Infrastructure
The domain was registered through CentralNic Ltd on 2026-09-08, only three days before PhishDestroy detected it. That short gap is typical of throwaway domains set up for a single campaign. Traffic runs through Cloudflare, Inc. (address 188.114.97.3, located in CA), which hides the server that actually hosts the page. The site uses a Google Trust Services certificate, so the browser padlock only means the connection is encrypted. It says nothing about whether the site is the real Laso Finance.
What to do
Do not connect a wallet to laso.cx or type anything into it. If you connected and signed anything, use a token-approval checker to revoke every permission granted around that time, and move remaining assets to a fresh wallet. If you entered a seed phrase, treat that wallet as compromised and empty it into a new one immediately. If you used a password there, change it on the real service and turn on two-factor authentication. Security teams should block the domain at DNS and email gateways and reach Laso Finance only through bookmarked or officially published addresses.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-19 22:30:47 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-19 22:35:34 UTClast content: 2026-10-19 22:30:47 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.
技术 · 4 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.
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.
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
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.
