VirusTotal
8 / 89 engine detections
Відкрити звіт“5MTBot — Automated Polymarket Bot for 5-Minute Crypto Rounds”
фішинг: 5mtbot.com — Контент недоступний. Зведення доказів: VirusTotal 8/89 (ChainPatrol, CRDF, Forcepoint ThreatSeeker, Gridinsoft, Kaspersky); 2 external…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
8 / 89 engine detections
Відкрити звітchecked — no detections recorded
Відкрити звіт4 community references
Відкрити звітprovider verdict: clean
Відкрити звіт80/100
Відкрити звіт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
5mtbot.com presented itself as "5MTBot — Automated Polymarket Bot for 5-Minute Crypto Rounds". It borrowed the Polymarket name to attract prediction-market users and short-term crypto traders looking for an automated edge. PhishDestroy first flagged it on 2026-09-13 and classifies it as impersonation phishing. The site has been offline since 2026-10-16, and its DNS was still inactive when we last checked on 2026-10-19.
The pitch is a bot that trades Polymarket's fast five-minute crypto rounds for you. That premise gives the site a reason to ask visitors to connect a wallet, fund the bot, or hand over account access. Schemes of this type turn that step into theft. Victims either sign wallet permissions that let the operator move their tokens, or they send deposits to a "bot balance" that never pays out. Either way, the loss is the crypto itself, not just login details.
Eight of 89 VirusTotal engines flagged the domain as of 2026-09-21: ChainPatrol, CRDF, Forcepoint ThreatSeeker, Gridinsoft, Kaspersky, Seclookup, SOCRadar and VIPRE. That count is modest, but several of those vendors specialize in crypto and phishing threats. The domain also appears on the MetaMask and SEAL blocklists alongside PhishDestroy, so wallet users were being warned from several directions. Four AlienVault OTX threat pulses reference it as well.
The domain was registered through Spaceship, Inc. on 2026-07-30, about 45 days before PhishDestroy detected it. That gap suggests a short-lived operation built to run for a few weeks. Traffic went through Cloudflare's network on an address geolocated to Canada, which hides where the real server sat. Its Let's Encrypt certificate gave visitors a padlock icon, but that only shows the connection was encrypted, not that the site was legitimate.
If you connected a wallet to 5mtbot.com, review its token approvals with a revocation tool and cancel any permissions you do not recognize. Move remaining funds to a fresh wallet if you signed anything unusual. If you sent a deposit to fund the "bot", treat it as lost and do not pay any fee promised to unlock withdrawals. Report the transaction to your wallet provider and to Polymarket. Security teams should block the domain, watch for lookalike "Polymarket bot" domains appearing on new registrations, and include the takedown in user awareness material.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
0x06dc51826bc524d9a83770e7de9dd7e005b04524Format validated · Domain analysis0x297200dfadee7d8daeb422faf0f62c238b37c110Format validated · Domain analysis0x388537259dc9e693c1c9b96fdf07a63f6b7aca77Format validated · Domain analysis0x6fd089a1556cdda1ad5efef08f997a03c7c0a85bFormat validated · Domain analysis0x765550c1f0af33254a2ac826710d33a4410c1fa8Format validated · Domain analysis0x952786297c560ebe88de2bac6ccf7cbcf531f108Format validated · Domain analysis0xc02acd7017071c895ac0a7ca923f14584beb10f8Format validated · Domain analysis0xc07c34a7f39f998cc63c6bac977a6ddbcfbdc4b7Format validated · Domain analysis0xf70eb753810c0ccea22a6948ebc3a541f04981dfFormat validated · Domain analysis0xfd9b5aceb381ab40b8a34a87bc5f2db5239f6eeaFormat validated · Domain analysisIoC extraction recorded 2026-09-13 04:00:08 UTC
Last checked
Репутація Edge-IP не пов’язана з цим доменом.
gina.ns.cloudflare.comharley.ns.cloudflare.comLocation describes the IP network.
a5b06adcbc983c45ced93387add93a2d4a6367feecc651ac29bb445648212bd6Saved 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 5mtbot.com · checked Sep 13, 2026
Verified files and their collected contents.
/robots.txt
/sitemap.xml
Type: urlset · 9 URL entries
https://5mtbot.com/https://5mtbot.com/bloghttps://5mtbot.com/blog/fee-update-october-2026https://5mtbot.com/blog/what-5mtbot-tradeshttps://5mtbot.com/blog/constellation-strategyhttps://5mtbot.com/blog/simple-and-advanced-strategyhttps://5mtbot.com/blog/settings-and-controlshttps://5mtbot.com/blog/how-trades-resolvehttps://5mtbot.com/privacyAn 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.
5mtbot.com
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
Доступний→Недоступно
redirected→dns_inactive
dns_nxdomain
Невідомо→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
Доступний
4 community references
View sourceNo threat flag
View source8/89 engine detections
View sourcePD-20260912-40F949
5mtbot.com
View sourcePage captured
View sourcePD-20260912-40F949 Recipient: abuse@spaceship.com Якщо ви ввели облікові дані облікового запису, особисту чи платіжну інформацію або завантажили файл із цього домену, негайно вживіть заходів. Нижче наведено ресурси, які допоможуть вам повідомити про інцидент і захистити себе.
Виберіть свою країну, щоб отримати офіційні контакти кіберзлочинців або створити проект скарги →.
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 ↗
5mtbot.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
Аналіз загроз за допомогою збереженого списку блокувань, 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.