VirusTotal
6 / 89 engine detections
レポートを開く“Vaultka - The Catalyst of Perpetual Exchanges on Arbitrum”
Arbitrumなりすまし: vaultkarewards.pages.dev — 到達可能・アクセス制限あり (HTTP 403). 証拠の概要: VirusTotal 6/89 (alphaMountain.ai, BitDefender, Forcepoint ThreatSeeker, G-Data…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
6 / 89 engine detections
レポートを開く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.
PhishDestroy threat report
vaultkarewards.pages.dev is an impersonation phishing page built for the Arbitrum DeFi crowd. It presented itself as "Vaultka - The Catalyst of Perpetual Exchanges on Arbitrum", and the "rewards" in its name points at users hoping to claim incentives. PhishDestroy first flagged it on 2026-09-05. The site has been offline since 2026-09-16 after the hosting provider blocked its content, and it was still dead at the last check on 2026-10-19.
The page copies the branding of a perpetual-exchange project on Arbitrum and wraps it in a rewards promise, so visitors expect to connect a wallet and collect something. Pages of this type then ask the visitor to approve a token allowance or sign a message that hands spending rights over their assets to the operator, and the wallet is emptied once that signature goes through. The page title carries Vaultka branding, while our classification records Arbitrum as the impersonated brand.
Six of 89 VirusTotal engines flagged the domain at the 2026-09-17 check: alphaMountain.ai, BitDefender, Forcepoint ThreatSeeker, G-Data, Gridinsoft and Webroot. That is a modest share, so many browsers and security products would not have warned visitors on their own. The crypto-specific lists filled that gap. ScamSniffer and Enkrypt block it alongside PhishDestroy, which matters because those lists protect users at the wallet level, right when a signature is requested.
The subdomain was created on Cloudflare Pages on 2026-09-04, and PhishDestroy caught it the next day. That timing fits a throwaway page set up to run briefly before anyone noticed. It was served from Cloudflare's network with a Canadian geolocation. Its Google Trust Services certificate came automatically with the platform, so the padlock said nothing about who was behind the page.
If you connected a wallet to this page and signed anything, revoke every approval granted around that time using a token-approval checker, then move any remaining funds to a fresh wallet. If you typed in a seed phrase, treat the wallet as compromised and transfer what is left right away. To check Vaultka or Arbitrum rewards, go only through the projects' official channels, never through a link someone sent you. Defenders should block the domain and watch for similar lookalike subdomains on free hosting platforms that pair DeFi project names with words like rewards or claim.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/vaultkaofficialStored page referenceIoC extraction recorded 2026-09-21 04:01:16 UTC
Last checked
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
121da2dcd84356081a0a5a6d2932515f96f7014776690f67978009a9bfbd199aSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
vaultkarewards.pages.dev
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
到達可能→利用不可
到達可能
No threat flag
View source6/89 engine detections
View sourcevaultkarewards.pages.dev
View source保存された類似ドメイン:28 件
コミュニティ報告:4 件
カテゴリPHISHING
@DrakardxAngel_cloaking_bot
“@DrakardxAngel_cloaking_bot”
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 ↗
vaultkarewards.pages.dev)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.