VirusTotal
8 / 92 engine detections
打开报告“株式会社HA-Na-Ko|住みなれた自宅で、これからも安心して暮らすために。”
冒充 MetaMask: hanako.app — 最后已知的活跃状态 (HTTP 200). 证据摘要: VirusTotal 8/92 (alphaMountain.ai, CRDF, CyRadar, Forcepoint ThreatSeeker, Fortinet); 2 external…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
8 / 92 engine detections
打开报告4 community references
打开报告provider verdict: clean
打开报告No threat flag
打开报告No malicious flag
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
hanako.app is an impersonation phishing page. It presents itself as "株式会社HA-Na-Ko", a Japanese company whose tagline promises help to keep living safely in your own familiar home. The page title reads as a home-care or senior-living service, while our classification is impersonation phishing. PhishDestroy first saw the domain on 2026-10-07, and it was still online with live content on 2026-10-19.
Impersonation pages borrow the look and wording of a legitimate business so visitors trust them enough to act. That action might be entering login details, personal information or payment data, or approving a request that looks routine. Here the lure is a reassuring Japanese corporate identity aimed at people looking after their homes or elderly relatives. Anything typed into the page should be treated as captured by the operator. MetaMask and SEAL both list the domain, so crypto wallet users are among the people it can reach.
On 2026-10-11, 8 of 92 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, CyRadar, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, SOCRadar and VIPRE. That is a minority of engines, but it is a varied group of independent vendors that reached the same verdict. Beyond PhishDestroy, the domain appears on the MetaMask and SEAL blocklists, which focus on threats to the crypto ecosystem. It is also referenced in 4 AlienVault OTX threat pulses.
The domain was registered on 2026-05-17 through CloudFlare, Inc. That is about four and a half months before PhishDestroy detected it, a longer runway than most throwaway phishing domains get. Traffic is served through Cloudflare's network with a Canadian geolocation, so the real origin server is hidden behind the proxy. The Let's Encrypt certificate gives the site a padlock, which only means the connection is encrypted, not that the business is genuine.
If you entered a password on hanako.app, change it right away on the real service and anywhere you reused it, and turn on two-factor authentication. If you shared card or bank details, contact your bank to block the card and dispute any charges. If you connected a crypto wallet or signed anything, revoke approvals you do not recognise and move funds to a fresh wallet if you typed a recovery phrase. Defenders should block the domain at DNS and the web proxy, and search mail and browsing logs for earlier visits.
Last checked
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Edge-IP 声誉不属于此域。
carlos.ns.cloudflare.comdiva.ns.cloudflare.com0live.sakura.ne.jppriority 10Location describes the IP network.
95244291345dd0a8f67ba45c993342245adb27e649b94b833ef49050a5f55d1aSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.hanako.appDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of hanako.app · checked Oct 7, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
可访问
No threat flag
View source8/92 engine detections
View source4 community references
View sourcehanako.app
View sourcePage captured
View source已存储 79 个仿冒域名
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
hanako.app
Listed domains receive at least one abuse report; this entry has no retained notification history.
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
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 ↗
hanako.app)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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
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.