VirusTotal
15 / 89 engine detections
レポートを開く“Cricfy TV — Watch Live Cricket Free on Android | IPL, PSL & T20 World Cup”
Amazonなりすまし: cricfy.cricket — コンテンツが利用できません (HTTP 451). 証拠の概要: VirusTotal 15/89 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar); Spamhaus…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
15 / 89 engine detections
レポートを開くDBL_PHISH
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
cricfy.cricket presented itself as "Cricfy TV — Watch Live Cricket Free on Android | IPL, PSL & T20 World Cup". It copied the name and pitch of a popular cricket streaming app to reach fans hunting for free match streams. PhishDestroy first flagged it on 2026-08-12. The site has been offline since 2026-10-06, and as of 2026-10-19 its content remains blocked by the provider.
Impersonation pages like this one count on people searching for a free way to watch big tournaments such as the IPL, PSL or T20 World Cup. The visitor lands on a page that looks like the real app's home. They are then pushed toward a download, a sign-up form or a sequence of prompts that the genuine brand does not control. Depending on what the operator is collecting, a victim can hand over login details or personal information, or install an Android package from an untrusted source.
On 2026-09-23, 15 of 89 VirusTotal engines flagged the domain. Those engines include BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, alphaMountain.ai, CRDF, CyRadar and Chong Lua Dao. The domain is also listed on the MetaMask and SEAL blocklists alongside PhishDestroy, and Spamhaus places it in its DBL under the phishing category. Four AlienVault OTX pulses reference it, so several independent researchers tracked it separately.
The domain was registered on 2026-06-17 through Fewmoretaps OU d/b/a Trustname.com, about eight weeks before PhishDestroy detected it. The .cricket extension was clearly chosen to make the address look like a natural home for a cricket app. The site sat behind Cloudflare, with the edge address geolocating to Canada. That setup keeps the real origin server out of view.
If you installed an app from this site, uninstall it and run a scan with a reputable mobile security tool. Check which permissions it was given, and get the genuine app only from an official store. If you created an account or typed a password there, change that password everywhere you reused it and turn on two-factor authentication. Watch for follow-up messages that use the Cricfy name. Security teams should block the domain at DNS and proxy level and look for similar cricket- and streaming-themed lookalikes on new extensions.
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 の評判はこのドメインに起因しません。
augustus.ns.cloudflare.comkelly.ns.cloudflare.comLocation describes the IP network.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of cricfy.cricket · checked Aug 12, 2026
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.
dead_http: raw=http_451; http=451; via=https_proxy; server=cloudflare
cricfy.cricket
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→blocked
http_451_blocked · http_451_unavailable
不明→blocked
http_451_blocked · http_451_unavailable
不明→blocked
http_451_blocked · http_451_unavailable
不明→blocked
http_451_blocked · http_451_unavailable
不明→blocked
http_451_blocked · http_451_unavailable
不明→blocked
http_451_blocked · http_451_unavailable
不明→blocked
http_451_blocked · http_451_unavailable
live_content→blocked
http_451_blocked · http_451_unavailable
到達可能→利用不可
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
到達可能
4 community references
View source15/89 engine detections
View sourceNo threat flag
View sourcecricfy.cricket
View sourcePage captured
View sourceListed 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 ↗
cricfy.cricket)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.