VirusTotal
11 / 89 engine detections
レポートを開く“Jpawe: Most Popular Online Crypto Casino Based on Blockchain”
暗号資産カジノ詐欺: jpawe.com — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 11/89 (alphaMountain.ai, BitDefender, CRDF, Ermes, Forcepoint ThreatSeeker); URLScan…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
11 / 89 engine detections
レポートを開くDBL_PHISH
悪意あり
レポートを開く4 community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
jpawe.com presents itself as "Jpawe: Most Popular Online Crypto Casino Based on Blockchain", but PhishDestroy classifies it as a fraudulent gambling site. It targets cryptocurrency holders who are looking for a blockchain casino. We first detected it on 2026-09-05. As of 2026-10-19 the site was still online and serving its casino pages.
The site runs on the Gambler Scam kit, a template for fake casinos that look polished but do not pay out. Victims are usually pushed toward a deposit, sometimes with a bonus or promo code. The account balance then shows winnings that grow quickly. When the player tries to cash out, the withdrawal is blocked, or new demands appear, such as "verification", tax or unlock fees that must be paid in crypto first. Every deposit and every extra fee goes straight to the operators and cannot be recovered.
Eleven of 89 VirusTotal engines flagged the domain when it was checked on 2026-09-13. The detecting vendors include BitDefender, Fortinet, Forcepoint ThreatSeeker, G-Data, Gridinsoft, alphaMountain.ai, CRDF and Ermes. That count may look modest, but it comes from established vendors, and other sources agree. urlscan.io returned a malicious verdict and tagged the page as a generic crypto scam. The domain is on the MetaMask and SEAL blocklists as well as PhishDestroy's own, Spamhaus lists it in its DBL as phishing, and it appears in four AlienVault OTX threat pulses.
The domain was registered on 2026-05-21 through Fewmoretaps OU (Trustname.com). That was about three and a half months before we caught it, long enough to set up the casino front and start drawing in players. Traffic passes through Cloudflare's network, with the visible address geolocated to Canada, so the real origin server is not exposed. The Let's Encrypt certificate only means the padlock icon is present. It says nothing about whether the casino is honest.
Do not deposit anything on jpawe.com. If you already did, do not pay any withdrawal, tax or verification fee, because those payments are simply taken as well. Save your transaction hashes, deposit addresses and any chat logs with "support". Report them to the exchange or wallet provider you sent funds from and to your local fraud authorities. Change any password you reused on the site. Defenders should block the domain, add the Gambler Scam kit's page title to detection rules, and watch for newly registered lookalike casino domains.
Last checked
Edge-IP の評判はこのドメインに起因しません。
barbara.ns.cloudflare.comchris.ns.cloudflare.comLocation describes the IP network.
3925555319813bb8bdee1e5a401a682443a968af57c94fab5fd75649bf8f145eSaved 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 jpawe.com · checked Sep 5, 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.
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
到達可能
4 community references
View sourceNo threat flag
View source11/89 engine detections
View sourcejpawe.com
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
jpawe.com
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 ↗
jpawe.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.