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@forticore.digital.
The latest stored availability evidence still shows the domain reachable; 13 days 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.
lockworth.me is on the PhishDestroy blocklist as a suspicious domain. Its page shows nothing but the title "Loading", so it does not openly present itself as any brand or service. PhishDestroy first detected it on 2026-10-06. As of 2026-10-19 the domain was still registered and live, but its DNS was no longer serving content.
How the scam works
We have not tied this domain to a specific scheme, and the "Loading" title shows no brand or offer. Blank pages with a generic loading title often appear on domains that only show their real content later, after a redirect, or to selected visitors. Because the domain is listed by vendors that track phishing and fraud, a visitor's main risks are being asked for credentials or seed phrases, or being prompted to connect a crypto wallet and sign requests that hand over control of funds.
Evidence
On 2026-10-10, 7 of 92 VirusTotal engines flagged the domain: alphaMountain.ai, Bfore.Ai PreCrime, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft and SOCRadar. That is a minority of engines, but the vendors are independent and include predictive and threat-intelligence services. Spamhaus lists it in its Domain Blocklist under the spam category. It also appears in 4 AlienVault OTX threat pulses, which shows that other researchers have tracked it.
Infrastructure
The domain was registered on 2026-09-06 through Global Domain Group LLC, exactly one month before PhishDestroy detected it. That short gap is common for disposable domains set up for one campaign. It resolved to 46.29.26.38, an address located in Finland on a network registered to M/S Robi Traders in Bangladesh. That mismatch between hosting location and network owner is worth noting for anyone correlating related infrastructure. The site used a free Let's Encrypt certificate, so the padlock in the browser says nothing about whether the site is trustworthy.
What to do
If you visited lockworth.me and entered a password, change it and turn on two-factor authentication on that account. If you typed a seed phrase or private key there, move your funds right away to a new wallet with a fresh seed. If you connected a wallet or signed anything, review and revoke token approvals you do not recognise. Defenders should block the domain and its IP, and search proxy and DNS logs for earlier lookups to find users who may have been exposed.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-20 10:06:51 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-09 10:07:13 UTClast content: 2026-10-09 10:07:13 UTCcurrent episode first observed: 2026-10-09 20:20:42 UTCobserved RIP window: 2026-10-09 10:07:13 UTC → 2026-10-09 20:20:42 UTC · 10.22hmidpoint estimate ≈ 2026-10-09 15:13:57 UTC · precision medium · 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.
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.
(US)
