VirusTotal
2 / 93 engine detections
Відкрити звіт“Polymarket | The World's Largest Prediction Market”
шахрайське криптоказино: polybeta.market — Контент недоступний. Зведення доказів: VirusTotal 2/93 (Gridinsoft, SOCRadar); URLQuery 1 alert; PhishDestroy score…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
2 / 93 engine detections
Відкрити звіт1 threat-system alert
Відкрити звітno 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.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Hagezi Threat Feed | polybeta.market |
malicious | Sinkholed |
PhishDestroy threat report
The domain polybeta.market was a phishing site engaged in brand impersonation, specifically targeting Amazon users to perpetrate a gambling scam. It posed as 'Polymarket | The World's Largest Prediction Market' but had no affiliation with the legitimate Polymarket platform or Amazon. No crypto drainer kit was detected. The site is currently taken offline.
Technical indicators confirm polybeta.market as a malicious domain. As of analysis, 2 of 95 VirusTotal security vendors flagged the domain, including Gridinsoft and SOCRadar, with a Gridinsoft trust score of 0/100. The domain was registered on 2026-02-21 through PDR Ltd. d/b/a PublicDomainRegistry.com and resolved to the IP address 104.21.3.187, hosted on Cloudflare's network (AS13335). No SSL certificate was issued. The domain appeared on three security blocklists: PhishDestroy, MetaMask, and SEAL. Nameservers were greg.ns.cloudflare.com and selah.ns.cloudflare.com.
Users who interacted with polybeta.market should take immediate safety steps. Since this was a gambling scam impersonating Amazon, victims should monitor their accounts for unauthorized transactions, change passwords, and enable two-factor authentication (2FA) on all financial and email accounts. Report the phishing domain to Amazon’s official fraud reporting channels, as well as to Google Safe Browsing, PhishTank, and local cybercrime authorities. If cryptocurrency was involved, revoke any token approvals and consider moving funds to a new wallet.
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 не пов’язана з цим доменом.
greg.ns.cloudflare.comselah.ns.cloudflare.comLocation describes the IP network.
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.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='polybeta.market', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
polybeta.market
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
https://radar.cloudflare.com/scan/15efe9f5-e600-4570-8fb8-8eb487cd820d
Page captured
View sourceNo threat flag
View source2/93 engine detections
View sourcepolybeta.market
View sourcePD-20260118-4EB20E
Повідомив 1 учасник спільноти; уперше помічено 18.01.2026
PD-20260118-4EB20E Recipient: abuse@publicdomainregistry.com Registrar: PublicDomainRegistry (PDR Ltd.) (India) Policy Violations: Explicit policy to immediately suspend domains used for phishing, 419 scams, identity fraud, malware distribution without prior notice Applicable Laws: IT Act 2000 §§66C–66D (identity theft, cheating by personation), Indian Penal Code §420 / Bharatiya Nyaya Sanhita §318 (fraud)
Якщо ви ввели облікові дані облікового запису, особисту чи платіжну інформацію або завантажили файл із цього домену, негайно вживіть заходів. Нижче наведено ресурси, які допоможуть вам повідомити про інцидент і захистити себе.
Виберіть свою країну, щоб отримати офіційні контакти кіберзлочинців або створити проект скарги →.
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 ↗
polybeta.market)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
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.