VirusTotal
19 / 92 engine detections
Mở báo cáo“Steam Community”
Giả mạo Counter-strike: frytt.dev — Hoạt động được biết đến lần cuối (HTTP 200). Tóm tắt bằng chứng: VirusTotal 19/92 (alphaMountain.ai, BitDefender, CRDF…
Phân tích chi tiết của PhishDestroy AI bên dưới được giữ bằng tiếng Anh để bảo toàn hồ sơ pháp chứng gốc.
19 / 92 engine detections
Mở báo cáoĐộc hại
Mở báo cáoĐộc hại
Mở báo cáoScan report
Mở báo cáono community references
Mở báo cáoNo threat flag
Mở báo cáoResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
PhishDestroy has placed frytt.dev on its internal blocklist as a suspicious domain. The domain was first observed by PhishDestroy on 2026-10-19. No page title was recorded for the site. Google Safe Browsing checked the domain on 2026-10-19 and did not flag it. An external blocklist, OpenPhish, also listed the domain as of the same date.
The current evidence does not point to a specific malicious mechanism. Suspicious domains like this can be used for phishing, credential harvesting, or fraud, but no particular behavior has been observed on frytt.dev. Without a concrete classification, the risk remains undefined and should be treated with caution.
VirusTotal retrieved on 2026-10-19 reported 19 detections out of 92 scanning engines, with vendors such as alphaMountain.ai, BitDefender, CRDF, CyRadar, Ermes, ESET, Emsisoft and Forcepoint ThreatSeeker flagging the site. Google Safe Browsing reported no threat on the same date. OpenPhish listed the domain, giving one external blocklist count. PhishDestroy’s internal list also includes frytt.dev. OTX showed zero pulses as of 2026-10-19.
The domain was registered on 2026-10-16 through Name.com, Inc. The recorded IP address is 88.80.135.136. The domain was observed three days after registration. No further network or hosting details are available.
If you visited the site, avoid entering any credentials or personal information and monitor accounts for unexpected activity. Change passwords for any services where credentials may have been submitted. Security teams should add frytt.dev to blocklists, review access logs for connections to the recorded IP, and apply standard web‑filtering policies to this exact address.
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.
ns1bqx.name.comns2glx.name.comns3fqs.name.comns4ksy.name.comLocation describes the IP network.
71fa946bf5aa814625c4780924419386beb5442f3dcfa467163df4f54909566ewww.frytt.devSaved 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.frytt.devDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of frytt.dev · checked Oct 19, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://frytt.dev/Server: nginxContent-Type: text/html; charset=utf-8Cache-Control: no-cacheContent-Encoding: gzip607ea6e6883404c7f835e4e270d4d46036c72fe0e7cfee4edc7323bf3f7b3319no-cachekeep-alivegziptext/html; charset=utf-8Mon, 19 Oct 2026 18:30:51 GMTnginxchunkedUser-AgentbrowserValues retained by the collector; long values may be shortened during collection.
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.
Không rõ→live_content
content_served
Có thể truy cập
PD-20261019-0D5110
Page captured
View sourceNo threat flag
View source19/92 engine detections
View sourcefrytt.dev
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
frytt.dev
PD-20261019-0D5110 Recipient: abuse@name.com Nếu bạn đã nhập thông tin xác thực tài khoản, thông tin cá nhân hoặc thông tin thanh toán hoặc đã tải xuống tệp từ miền này, hãy hành động ngay lập tức. Dưới đây là các nguồn lực giúp bạn báo cáo vụ việc và bảo vệ chính mình.
Chọn quốc gia của bạn để nhận liên hệ tội phạm mạng chính thức hoặc soạn thảo đơn khiếu nại →.
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 ↗
frytt.dev)Dù bạn chưa nắm rõ tất cả các chi tiết — vẫn nên nộp báo cáo. Ngay cả những thông tin không đầy đủ cũng vẫn có ích cho công tác điều tra.
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
Phân tích mối đe dọa bằng cách sử dụng danh sách chặn được lưu trữ, WHOIS, DNS và bằng chứng quét công khai
Quét ngayHãy gửi các tên miền đáng ngờ đến cơ sở dữ liệu mối đe dọa của chúng tôi — để bảo vệ cộng đồng
Báo cáoCác báo cáo lừa đảo gần đây và những thay đổi về tính khả dụng được quan sát thấy
Theo dõiTheo dõi các mối đe dọa đang diễn ra hoặc phản đối danh sách này nếu bạn cho rằng đây là kết quả báo động sai
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.