セキュリティレポートへ移動
ドメインのセキュリティと脅威インテリジェンス
gxmcoinbm.com favicon

gxmcoinbm.com

レジストラ
Name.com
Resolved IP
172.67.172.68
Registered
2026年4月25日
PhishDestroy assessment クリティカル
First observed Sep 8, 2026 16:40 UTC · PhishDestroy
VirusTotal 検出数: 4/89 自動ブランドラベル:Google
OTX: 3 refs 2026年9月8日 CDN
API
このドメインは悪意のあるものとして報告されています
検出を報告するセキュリティ エンジン: 4。 細心の注意を払ってください — 資格情報や個人情報を入力しないでください。
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Domain age
レポート概要

Googleなりすまし: gxmcoinbm.com — 未検証. 証拠の概要: VirusTotal 4/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, SOCRadar); PhishDestroy score 81/100. レジストラ…

元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。

Source evidenceVirusTotal 4 / 89 · OTX 3 references 4 sources

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

クリティカル
VirusTotal
4 / 89
OTX
3 community refs

PhishDestroy threat report

Overview

gxmcoinbm.com is an impersonation phishing site. Its name is built to look like a crypto coin or trading service, and it targets people who believe they are signing in to or funding a legitimate account. PhishDestroy first flagged it on 2026-09-08. On 2026-10-19 the host was still responding, but the domain's DNS no longer pointed to active content, so the page may be dormant rather than gone for good.

How the scam works

An impersonation page copies the look and wording of a service the victim already trusts. It then asks for exactly what that service would ask for: account credentials, a one-time 2FA code, a deposit, or in crypto schemes a recovery phrase. Anything typed into the page goes straight to the operators. Stolen logins are used to empty the real account, deposits sent to addresses shown on the page are gone, and a revealed seed phrase hands over the whole wallet.

Evidence

Detection is thin. On 2026-09-21, 4 of 89 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker and SOCRadar. PhishDestroy is the only blocklist carrying it, so many browsers and filters will still let it through. Three AlienVault OTX threat pulses reference the domain, which shows other researchers have tied it to malicious activity independently.

Infrastructure

The domain was registered through Name.com, Inc. on 2026-04-25, about four and a half months before it was detected. That gap fits a domain held in reserve until a campaign is ready to launch. It sits behind Cloudflare, Inc., with the visible address placed in Canada, so the origin server that actually hosts the page is hidden from view.

What to do

If you entered a password on this site, change it on the genuine service immediately and anywhere else you reuse it. Then reset your 2FA and review recent logins and withdrawals. If you typed a recovery phrase, treat that wallet as compromised and move any remaining funds to a new wallet created from a fresh phrase. If you sent a deposit, do not pay any follow-up "fee" to release it. Report the transfer to your exchange and to local police. Defenders should block the domain at DNS and proxy level, since most blocklists do not yet catch it. They should also search mail and web logs for any users who reached it.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Domain details

ドメイン
IP Context Cloudflare shared edge origin IP hidden Edge-IP の評判はこのドメインに起因しません。
OTX tags 2026-09activeall-domainsblocklistcontentcryptoドメインdrainerfraudmonthlyphishdestroyphishingscam
レジストラ Name.com US(US)
不正利用連絡先["abuse@name.com"]
ICANNレジストリICANN Lookup (RDAP) →
登録情報作成日 2026年4月25日 (177d) — Expires 2027年4月25日
技術詳細Provenance & timestamps
初確認2026年9月8日
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
172.67.172.68
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP の評判はこのドメインに起因しません。

ネームサーバー 1

  • fay.ns.cloudflare.com

Location describes the IP network.

TLS証明書

Issuer
Google Trust Services / WE1
Valid from
2026-08-26 10:10:30
Valid until
2026-11-24 11:10:19
Validity
Within stored validity dates
Collection time
2026-10-20 16:02:23 UTC
Collection source
PhishDestroy collector
Certificate fingerprint5d0cdc9e7bafb18cd0826e483bf4ea88380188ae20feecfb3ada1be48f40497c

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-20 08:21:37 UTC

Primary outcome DNS 非アクティブ reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation 不明 Probe Inconclusive 20% 2026-10-20 10:07:29 UTC
RDAP registration 不明
Observed timeline last reachable: 2026-10-08 10:11:04 UTC last content: 2026-10-08 10:11:04 UTC current episode first observed: 2026-10-08 20:20:32 UTC observed RIP window: 2026-10-08 10:11:04 UTC → 2026-10-08 20:20:32 UTC · 10.16h midpoint estimate ≈ 2026-10-08 15:15:48 UTC · precision medium · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
使用技術 · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
このドメインを報告する 証拠を提出し、他の人を守る手助けをしましょう

VirusTotalによる分析

4 / 89 セキュリティ ベンダーがこのドメインにフラグを立てました
View on VT
Last analyzed First positive detection Previous stored snapshot: 4 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
SOCRadar
サイトパフォーマンス分析

Google PageSpeed Insights — mobile performance audit of gxmcoinbm.com · checked Sep 15, 2026

99
Good
Performance
FCP
1.55s
First Contentful Paint
LCP
1.55s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.55s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details9

Availability observations

Last reachable observation
Last content observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
10.16
Estimate basis
Bounded by observations
Estimate precision
中

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history20

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

Earlier observations 15
  1. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  7. Availability monitor · Recorded state

    live_content→dns_inactive

    dns_nxdomain

  8. Availability monitor · Recorded state

    不明→live_content

    content_served

  9. Availability monitor · Recorded state

    不明→live_content

    content_served

  10. Availability monitor · Recorded state

    不明→live_content

    content_served

  11. Availability monitor · Recorded state

    不明→live_content

    content_served

  12. Availability monitor · Recorded state

    不明→live_content

    content_served

  13. Availability monitor · Recorded state

    不明→live_content

    content_served

  14. VirusTotal · Detection count

    1→4

  15. Availability monitor · First collection record

    到達可能

Recorded activity

4 entries
  1. AlienVault OTX

    3 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    4/89 engine detections

    View source
  4. Added to PhishDestroy

    gxmcoinbm.com

    View source

コミュニティ情報

コミュニティ報告:1 件

カテゴリFAKE_PROJECT

On August 9, 2026, I lost approximately $1,100 USD in a cryptocurrency investment scam. I was contacted/approached by individuals associated with the TSQ Group and was deceived into believing that GXMCOIN was a legitimate cryptocurrency investment platform. I purchased 1,049.1

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

gxmcoinbm.com

証拠および外部報告書

Community Scam Report — ChainAbuse
1 report filed for gxmcoinbm.com (1 written by a person) · category: Fake Project · source checked
“On August 9, 2026, I lost approximately $1,100 USD in a cryptocurrency investment scam. I was contacted/approached by individuals associated with the TSQ Group and was deceived into believing that GXMCOIN was a legitimate cryptocurrency investment platform. I purchased 1,049.19 USDT through MoonPay for a total cost of $1,100 USD using Apple Pay. The USDT was delivered to my Trust Wallet and I was then instructed to transfer it to a wallet associated with the fraudulent platform. I transferred”
— reported by Anonymous on Sep 8, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
詳細な分析
Help & reporting

このサイトによって何か影響を受けましたか?

2 evidence signal groups linked 0 stored notification records 未検証

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。

Official reporting routes

復旧を装った詐欺に注意! 犯罪者は、捜査員、弁護士、または回収業者を装い、被害者に再び連絡を取る可能性があります。 前払い料金を支払ったり、資格情報を共有したりしないでください。 回復詐欺について詳しくはこちら →

お住まいの地域の当局へ報告してください

サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。

97か国のディレクトリ

Template-based draft · optional AI wording assistance requires separate consent

AI 支援ドラフト — インシデントの詳細は AI プロバイダーによって処理されます · 自分で確認して送信する
After a phishing incident

被害者への推奨事項とアドバイス

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.

  • すべてのパスワードを変更する — メール、Exchangeアカウントなど、同じパスワードを使用しているものすべて
  • 2段階認証を有効にする 認証アプリ(SMSではない)を使用する。SMSによる復旧機能を無効にする
  • カードの凍結 フィッシングサイトに銀行口座情報を入力してしまった場合

レポート作成のために、どのような情報を収集すべきでしょうか?

FBIのガイドライン

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • 正確な日時 — 各取引および詐欺師との最初の接触について
  • スクリーンショット — 詐欺サイト、チャットメッセージ、メール、ウォレットでの取引、ソーシャルメディア
  • すべてのURLおよびドメイン 詐欺師が使用した(以下を含む) gxmcoinbm.com)
  • コミュニケーション — 詐欺師が使用したメール、テキストメッセージ、電話番号、ユーザー名

たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。

この詐欺はどこに通報すればいいですか?

  • FBI IC3 — インターネット犯罪通報センター(米国連邦政府の通報窓口)
  • ユーロポール — 欧州におけるサイバー犯罪の報告(EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • 地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • 偽のウェブサイト — 正規サイトのドメインをわずかに変更した、ピクセル単位で完璧に再現されたクローンサイト
  • pig butchering — TelegramやWhatsApp、出会い系アプリを通じて数週間にわたって信頼関係を築き、その後、金銭をだまし取られる
  • 詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AIを利用した詐欺 — ディープフェイク、自動化されたフィッシング、AI生成サイトにより、詐欺の発見が難しくなっている

今後、どうすれば身を守ることができるでしょうか?

  • 公式サイトをブックマークする — メール、DM、広告に含まれるリンクは絶対にクリックしないでください
  • ドメインの確認 — 確認する PhishDestroy 操作を行う前に、HTTPS、スペル、ドメインの登録期間を確認してください。
  • 「良すぎて怪しい」=詐欺 — 確実なリターン、有名人の推薦、差し迫った締め切り

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

最新情報を入手し、安全を確保しましょう

リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください

リアルタイム脅威情報フィード この掲載情報について異議を申し立てる
About this reportSources, observation dates and corrections

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

このレポートを埋め込む

この脅威情報を、ご自身のウェブサイトやブログで共有してください

embed.html
<iframe
  src="https://phishdestroy.io/ja/embed/domain/gxmcoinbm.com"
  title="PhishDestroy threat report for gxmcoinbm.com"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>