VirusTotal
17 / 89 engine detections
打开报告“🐹 HamsterCombat · тапалка”
钓鱼: flixstash.com — 最后已知的活跃状态 (HTTP 301). 证据摘要: VirusTotal 17/89 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar); CF Radar malicious…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
17 / 89 engine detections
打开报告恶意
打开报告5 community references
打开报告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
flixstash.com poses as Hamster Combat, the Telegram tap-to-earn game, under a page title that reads "🐹 HamsterCombat · тапалка". The Russian word means "tapper", which suggests the page targets Russian-speaking players. The domain name has nothing to do with the game, a common sign of a throwaway phishing host. PhishDestroy first flagged it on 2026-09-05, and it was still alive on 2026-10-19, now serving its content through a redirect.
Hamster Combat clones bait players with what looks like their familiar game, then promise bonus coins, token claims or airdrop eligibility. To claim the reward, the victim is asked to log in, hand over account details, or connect a crypto wallet and sign what is presented as a routine confirmation. Depending on the step, the victim can lose their Telegram or game account, or the tokens held in the connected wallet. The redirect means the visible domain may only be the entry point, with the actual lure loading elsewhere.
On 2026-09-18, VirusTotal showed 17 of 89 engines flagging the domain. That is a strong result for a site with a forgettable name. The vendors include BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, alphaMountain.ai, CRDF, CyRadar and the Vietnamese anti-scam group Chong Lua Dao. The domain also appears in 5 AlienVault OTX threat pulses, so other researchers have tied it to tracked malicious activity. PhishDestroy lists it on its blocklist.
The domain was registered on 2026-06-25 through Trustname.com (Fewmoretaps OU), about ten weeks before PhishDestroy first saw it. That gap fits a domain bought ahead of time and held until a campaign needed it. It resolves to 45.12.62.34 on the MHost LLC network in the Netherlands. Its Let's Encrypt certificate gives it a browser padlock, which proves nothing about who runs the site.
If you connected a wallet to this site, use a token-approval checker to revoke any permissions it requested. Move remaining funds to a fresh wallet if you signed anything you did not understand. If you entered Telegram or game login details, end unknown sessions in Telegram settings, enable two-step verification and change any reused passwords. Remember that Hamster Combat rewards are claimed only inside the official Telegram bot, never on outside websites. Defenders should block the domain and its IP, and watch for further Hamster Combat lures on unrelated domain names.
ares.trustname.comns1.anycastdns.czns2.anycastdns.czzeus.trustname.comLocation describes the IP network.
66e8a88d17e891222e46036542db00f4784d9f53a9b1541b86d6082b29658e27minet2.krusofiya.funSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
redirect: raw=redirect_301; http=301; via=http_proxy; location=https://flixstash.com/; server=nginx
flixstash.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
18→17
可访问
5 community references
View sourceNo threat flag
View source17/89 engine detections
View sourceflixstash.com
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 ↗
flixstash.com)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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.