VirusTotal
10 / 92 engine detections
रिपोर्ट खोलें“Bot Verification”
Binance की नकल: xm-signal.live — अंतिम ज्ञात सक्रिय (HTTP 200). साक्ष्य सारांश: VirusTotal 10/92 (alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint…
मूल फॉरेंसिक रिकॉर्ड सुरक्षित रखने के लिए नीचे का विस्तृत PhishDestroy AI विश्लेषण अंग्रेज़ी में रखा गया है।
10 / 92 engine detections
रिपोर्ट खोलेंSuspicious
रिपोर्ट खोलें2 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
xm-signal.live is an impersonation phishing site whose name suggests a trading-signals service, the kind of lure used against crypto and trading users. Visitors first see a page titled "Bot Verification" rather than the content it imitates. PhishDestroy first saw the domain on 2026-10-09. As of 2026-10-19 the site was still online, with its content reachable only behind that protective gate.
Impersonation pages borrow the look and name of a trusted service so victims hand over what that service would normally ask for, such as login credentials, recovery details or a wallet connection. Here a "Bot Verification" screen comes first, a familiar step that lowers suspicion before the real page loads. The page title points to a verification check, while our classification is impersonation phishing. Victims risk losing account access, funds or whatever they type into the copied interface.
MetaMask and SEAL, two crypto-focused security groups, list this domain on their blocklists alongside PhishDestroy. That puts it squarely in the wallet-phishing space. On 2026-10-13, 10 of 92 VirusTotal engines flagged it. Among them were alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data and Gridinsoft. Detection is therefore still partial, and many security tools will not warn visitors. The domain also appears in two AlienVault OTX threat pulses, so other researchers have tied it to malicious activity.
The domain was registered on 2026-10-02 through TuringSign Inc. d/b/a Cosmotown, just seven days before PhishDestroy detected it. That short gap is typical of throwaway phishing domains set up for a single campaign. It is hosted in the US on the Aquiryn LLC network. It uses a free automated certificate, so the padlock in the browser says nothing about whether the site is legitimate.
If you entered a password or login on this site, change it at once on the real service, and anywhere you reused it. Then turn on app-based 2FA. If you connected a crypto wallet or approved a transaction, revoke any token approvals you do not recognize with a trusted approval checker. If you shared a seed phrase, move your funds to a new wallet immediately. Defenders should block the domain and its hosting IP at the DNS and proxy level, and warn users that a "Bot Verification" screen is not proof a site is safe.
Stored page, network and scanner observations, grouped by source and observation time.
निरीक्षित: · Retrieved:
| Uuid | 01a11501-ba3c-742b-8179-102b03f37239 |
|---|---|
| Final url | https://xm-signal.live/ |
| स्थिति | 200 |
| Ip | 23.153.104.17 |
| Ptr | c4-17.my-control-panel.com |
| Contacted domains | [
"www.youtube.com",
"coin-images.coingecko.com",
"fonts.gstatic.com",
"www.cryptocompare.com",
"jnn-pa.googleapis.com",
"googleads.g.doubleclick.net",
"static.getbutton.io",
"cdn.gtranslate.net",
"use.fontawesome.com",
"i.ytimg.com",
"www.google.com",
"static.doubleclick.net",
"widgets.cryptocompare.com",
"api.coingecko.com",
"fonts.googleapis.com",
"code.tidio.co",
"widgets.coingecko.com"
] |
| Contacted IP addresses | [
"104.18.30.136",
"172.217.119.4",
"142.251.20.119",
"142.251.156.119",
"192.178.183.148",
"142.251.20.155",
"172.67.142.173",
"104.26.14.221",
"142.251.150.4",
"20.126.215.223",
"172.66.172.219",
"142.251.14.94",
"142.250.154.95",
"172.67.73.221",
"104.18.4.118"
] |
| Asns | [
"13335",
"15169",
"8075",
"32561"
] |
| Countries | [
"US",
"NL"
] |
| Linked domains | [
"www.blockchain.com",
"www.cryptocompare.com",
"wa.me",
"getbutton.io"
] |
| Social | [
"https://wa.me/573237409893"
] |
| Document hash | dbbe388766281a35e6ecfea65210bd3f4aca29b88d6111731e0388d58ea9af80 |
| Script hashes | [
"160a426ff2894252cd7cebbdd6d6b7da8fcd319c65b70468f10b6690c45d02ef",
"587c080125b135d29a931ed371e50ffc1a9641831c1087de2cd74532815f4560",
"eb795deda8983fa5310627c9584cf3f3b95d272567113500059018b3941cb267",
"23fc25133ed072cdf7dae575213067b1da3c6843b2a0e489c8b7fc984c60ce6b",
"1fd8c0cfffd02e40cecbf9f313d1b86988a342d90bb7d16f1a67544f0064ea0b",
"f2beb92898142c10e2661c03c9d7d6ac4931df2c95fe0ac6b06cda7a4a1b9e02",
"96abf166b3cbb5f7df525d86fdeeeccea4af3c120b19bc26b0613530a94e8b44",
"186e4c2c470e3c1c76997b7a4dfd0f618b38311582e0578db05ccada6fd43c6c",
"f5118c2117300dcd406002417f201608dc046ee26b0680d4c1c93ecd01d7cc2d"
] |
| Globals | [
"$",
"jQuery",
"Popper",
"bootstrap",
"moment",
"EvEmitter",
"imagesLoaded",
"gtranslateSettings",
"__core-js_shared__",
"core",
"nav",
"functionConfirm",
"scripts",
"embedder",
"baseUrl",
"doGTranslate",
"setImmediate",
"clearImmediate",
"GBBTN",
"WhWidgetSendButton",
"fabric",
"saveAs",
"XLSX",
"XLS",
"cccCurrentTheme",
"cccCreateCSSSelector",
"cccglobal_data",
"cccupdating",
"cccloading_counter",
"cccfsym",
"ccctsym",
"cccscale",
"ccclimit",
"cccperiod",
"cccaggregate",
"cccminPeriod",
"cccforceAll",
"cccchart_type",
"chartBTC",
"colors"
] |
| कुकीज़ | [
"XSRF-TOKEN",
"xm_signals_session",
"__Secure-YNID",
"YSC",
"__Secure-ROLLOUT_TOKEN",
"VISITOR_INFO1_LIVE",
"VISITOR_PRIVACY_METADATA",
"__cf_bm"
] |
| Tls | {
"san": [
"*.xm-signal.live",
"xm-signal.live"
],
"cipher": "AES_128_GCM",
"issuer": "YR2",
"subject": "xm-signal.live",
"protocol": "TLS 1.3",
"valid_to": "2027-01-01T15:08:21Z",
"valid_from": "2026-10-03T15:08:22Z"
} |
| Domain age days | 3 |
| Apex age days | 3 |
| Tls age days | 3 |
| Tls valid days | 89 |
| Requests | 76 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 100,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "LiteSpeed",
"content-type": "text/html; charset=UTF-8"
} |
निरीक्षित: · Retrieved:
| Uuid | d8220563-9d55-49e4-b3ba-e3fd5eec3ad8 |
|---|---|
| Final url | https://xm-signal.live/ |
| स्थिति | 200 |
| History | [
{
"url": "https://xm-signal.live/",
"status": 200
}
] |
| DOM structure hash | bda6616060ca5cd35f1fbf6c7906c9ed8677e304707a22bc7e390aa5f32174bb |
| Document hash | 5928439965443ca5ab0926118ae67648994b73f3837dca07c3fc20843be3f7ef |
| Phishing v2 | [
"phishing"
] |
| Url risks | [
"Scam"
] |
| Domain risks | [
"Scam",
"Security threats",
"Newly Seen Domains",
"Security Risks",
"New Domains",
"CIPA Filter",
"CIPA"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "xm-signal.live",
"type": "A",
"value": "23.153.104.17"
}
] |
| Dnssec valid | false |
| Ip | 23.153.104.17 |
निरीक्षित: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 49,
"malicious": 7,
"suspicious": 2,
"undetected": 34
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"ESET": "phishing",
"G-Data": "phishing",
"Fortinet": "spam",
"Netcraft": "malicious",
"Gridinsoft": "suspicious",
"BitDefender": "phishing",
"alphaMountain.ai": "phishing",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Categories | {
"alphaMountain.ai": "Phishing, Newly Registered (alphaMountain.ai)"
} |
| First seen | 2026-10-03T21:33:15Z |
| DNS records | [
{
"ttl": 14400,
"type": "TXT",
"value": "v=spf1 +a +mx +ip4:192.168.168.2 ~all"
},
{
"ttl": 11990,
"type": "NS",
"value": "ns7.my-control-panel.com"
},
{
"ttl": 21600,
"type": "SOA",
"rname": "admin.my-control-panel.com",
"value": "ns7.my-control-panel.com"
},
{
"ttl": 14400,
"type": "MX",
"value": "xm-signal.live",
"priority": 0
},
{
"ttl": 14400,
"type": "A",
"value": "23.153.104.17"
},
{
"ttl": 11990,
"type": "NS",
"value": "ns8.my-control-panel.com"
}
] |
| Dns at | 2026-10-14T07:18:56Z |
| Jarm | 29d29d00029d29d00042d43d00041d598ac0c1012db967bb1ad0ff2491b3ae |
| Certificate | {
"san": [
"*.xm-signal.live",
"xm-signal.live"
],
"issuer": "Let's Encrypt / YR2",
"serial": "52ff24715450f20a6b236d88008f68928e",
"sha256": "35b41fae9b3cbeb381aad3b4f20415826850887dff34efe3910c69fc75534c43",
"subject": "xm-signal.live",
"valid_to": "2027-01-01T15:08:21Z",
"valid_from": "2026-10-03T15:08:22Z"
} |
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.
ns8.asurahosting.comxm-signal.livepriority 0Location describes the IP network.
35b41fae9b3cbeb381aad3b4f20415826850887dff34efe3910c69fc75534c43*.xm-signal.livexm-signal.liveSaved 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 xm-signal.live · checked Oct 9, 2026
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.
अज्ञात→protected
captcha · challenge
अज्ञात→protected
captcha · challenge
अज्ञात→protected
captcha · challenge
अज्ञात→protected
captcha · challenge
protected→live_content
content_served
अज्ञात→protected
captcha · challenge
अज्ञात→protected
captcha · challenge
protected→live_content
content_served
अज्ञात→protected
captcha · challenge
अज्ञात→protected
captcha · challenge
अज्ञात→protected
captcha · challenge
अज्ञात→protected
captcha · challenge
अज्ञात→protected
captcha · challenge
No threat flag
View source10/92 engine detections
View source2 community references
View sourcexm-signal.live
View source187 संग्रहीत मिलते-जुलते डोमेन
187 में से 100 दिखाए जा रहे हैं
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
xm-signal.live
Listed 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 ↗
xm-signal.live)भले ही आपके पास सभी विवरण न हों — फिर भी रिपोर्ट दर्ज करें. आंशिक जानकारी अभी भी जांच में मदद करती है।
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.