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

secure-help-com.zapier.app

“Coinbase.com || Log In**”

レジストラ
Name.com
Resolved IP
64.239.109.193
Registered
2022年9月20日
PhishDestroy assessment クリティカル
可用性 最後に確認されたアクティブな状態 最新の保存された到達可能性の観測 観測された · HTTP probe
VirusTotal 検出数: 14/91 自動ブランドラベル:Coinbase
2026年9月17日 CDN
API
このドメインは悪意のあるものとして報告されています
検出を報告するセキュリティ エンジン: 14。 細心の注意を払ってください — 資格情報や個人情報を入力しないでください。
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Domain age
レポート概要

Coinbaseなりすまし: secure-help-com.zapier.app — 最後に確認されたアクティブな状態 (HTTP 308). 証拠の概要: VirusTotal 14/91 (ChainPatrol, alphaMountain.ai, Ermes, ESET, Emsisoft)…

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

Source evidenceVirusTotal 14 / 91 6 sources

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

ネットワークセキュリティインテリジェンス
CF Cloudflare Radar Verdict 悪意あり
Phishing

Analysis

クリティカル
VirusTotal
14 / 91
Page captures
2

PhishDestroy threat report

Overview

secure-help-com.zapier.app is a phishing page that impersonates Coinbase. It presents itself as the exchange's sign-in screen under the tab title "Coinbase.com || Log In". It targets Coinbase customers, and the "secure-help" label is aimed at people looking for account support. PhishDestroy first flagged it on 2026-09-17, and the site was still live when last checked on 2026-10-19.

How the scam works

Victims usually arrive through a link presented as a security alert or a support response. The page imitates the Coinbase login form, so anything typed into it goes to the operator, not to Coinbase. Pages like this often ask next for a one-time 2FA code or a recovery step, which lets the attacker sign in to the real account right away. The stolen login is then used to move crypto out of the victim's Coinbase account.

Evidence

On 2026-09-29, 14 of 91 VirusTotal engines flagged the page. The flagging vendors include ChainPatrol, ESET, Fortinet, Forcepoint ThreatSeeker, Emsisoft, Gridinsoft, Ermes and alphaMountain.ai. That is a minority of engines, but several of them, ChainPatrol in particular, focus specifically on crypto phishing. urlscan.io returned a malicious verdict and detected Coinbase branding on the page, which independently confirms the impersonation. PhishDestroy lists the domain on its blocklist.

Infrastructure

The page is a subdomain of zapier.app, so its address borrows the reputation of a well-known automation platform's hosting space. The registration date of 2022-09-20 and the registrar Name.com, Inc. belong to the parent zapier.app domain, not to this scam, so the domain's age says nothing about when the phishing page appeared. The site resolves to Amazon.com, Inc. infrastructure in the US and uses a Let's Encrypt certificate. The browser padlock therefore only means the connection is encrypted, not that the site is legitimate.

What to do

If you entered your Coinbase email and password here, change your password immediately from the official Coinbase app or a bookmarked address. Then end all active sessions and review your account for new devices, API keys or withdrawal addresses. If you also gave a 2FA code, assume the account was accessed: contact Coinbase support through its official channels and switch to an authenticator app or security key. If you reused that password anywhere else, change it there too. Security teams should block the subdomain, search mail and proxy logs for visits to it, and report it to Zapier and Coinbase so it can be taken down.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

保存済みキャプチャ · 2 captures

Observed page title
Coinbase.com || Log In**
Automated brand references
Apple Coinbase Ethereum Google
TLS証明書
発行者 Let's Encrypt / YR1 · stored validity ends in 30 days

Domain details

ドメイン
URLScan verdict 悪意あり score 100 Phishing brand: Coinbase report ↗
IP Context Vercel shared edge origin IP hidden Edge-IP の評判はこのドメインに起因しません。
Registrar (base domain) Name.com US(US)
不正利用連絡先["abuse@name.com"]
ICANNレジストリICANN Lookup (RDAP) →
Registration (base domain)zapier.app · 作成日 2022年9月20日 — Expires 2027年9月20日
HTTPステータス308 Permanent Redirect
技術詳細Provenance & timestamps
初確認2026年9月17日
DOM Analysisanalyzed 2026年9月17日score 88/1004 brand signals
Submitted URLhttp://secure-help-com.zapier.app/
Favicon Hash
ICANN OVERSIGHT Registration: zapier.app

認定と RAA の背景

Registrar accreditation and DNS abuse obligations

For the registrable domain zapier.app behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

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.

Accountability draft 自動送信は一切行われません。

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
64.239.109.193
Network ASN
AS16509
Organization
Vercel, Inc
Observed location
Walnut, US
Server header
Vercel

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

ネームサーバー 1

  • ns2.vercel-dns.com

Location describes the IP network.

TLS証明書

Issuer
Let's Encrypt / YR1
Valid from
2026-08-22 02:51:05
Valid until
2026-11-20 02:51:04
Validity
Within stored validity dates
Collection time
2026-10-11 01:03:59 UTC
Collection source
PhishDestroy collector
Certificate fingerprinta813a4e503b35535fb96a4c8df328eb445fdbba2e1686ddb446de1bec037f88f

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 10:06:53 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-20 10:06:53 UTC
RDAP registration 不明
Observed timeline last reachable: 2026-10-20 10:06:53 UTC
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.
使用技術 · 6 identified
Detected via Cloudflare Radar · Wappalyzer engine
このドメインを報告する 証拠を提出し、他の人を守る手助けをしましょう

VirusTotalによる分析

14 / 91 セキュリティ ベンダーがこのドメインにフラグを立てました
View on VT
Last analyzed First positive detection Previous stored snapshot: 16 detections
ChainPatrol
alphaMountain.ai
Ermes
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
LevelBlue
Lionic
ネットクラフト
ソフォス
VIPRE
Webroot

アーカイブ済み証拠

Wayback Machine Snapshot
過去のスナップショットは証拠のレビューに利用可能です
View Archive
サイトパフォーマンス分析

Google PageSpeed Insights — mobile performance audit of secure-help-com.zapier.app · checked Sep 17, 2026

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

Availability observations

Last reachable observation
Estimate basis
Currently reachable

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

Check for cloaking

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

secure-help-com.zapier.app
保存済みの結果
Cloaked / Filtered
Stored observation history21

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

    不明→redirected

    http_redirect

  2. Availability monitor · Recorded state

    不明→protected

    http_access_restricted · access_restriction

  3. Availability monitor · Recorded state

    redirected→protected

    http_access_restricted · access_restriction

  4. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  5. Availability monitor · Recorded state

    不明→redirected

    http_redirect

Earlier observations 16
  1. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  2. Availability monitor · Recorded state

    protected→redirected

    http_redirect

  3. Availability monitor · Recorded state

    不明→protected

    http_access_restricted · access_restriction

  4. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  5. Availability monitor · Recorded state

    不明→protected

    http_access_restricted · access_restriction

  6. Availability monitor · Recorded state

    redirected→protected

    http_access_restricted · access_restriction

  7. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  8. Availability monitor · Recorded state

    redirected→protected

    http_access_restricted · access_restriction

  9. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  10. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  11. Availability monitor · Recorded state

    利用不可→到達可能

  12. Availability monitor · Recorded state

    不明→inactive

    http_no_content

  13. Availability monitor · Recorded state

    不明→inactive

    http_no_content

  14. Availability monitor · Recorded state

    不明→inactive

    http_no_content

  15. Availability monitor · Recorded state

    到達可能→利用不可

  16. VirusTotal · Detection count

    15→16

Recorded activity

3 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    14/91 engine detections

    View source
  3. Added to PhishDestroy

    secure-help-com.zapier.app

    View source

類似ドメイン

保存された類似ドメイン:255 件

すべて表示(88)
coinbaso.com vowel-swap coinbose.com vowel-swap coinbuse.com vowel-swap conibase.com transposition cuinbase.com vowel-swap ocinbase.com transposition c9inbase.com replacement ccoinbase.com repetition ciinbase.com replacement cinbase.com omission cionbase.com transposition clinbase.com replacement co8nbase.com replacement co9nbase.com replacement coi.nbase.com subdomain coibase.com omission coibbase.com replacement coihbase.com replacement coinase.com omission coinb.ase.com subdomain coinb1se.com replacement coinb2se.com replacement coinbaae.com replacement coinbade.com replacement coinbaee.com replacement coinbas.com omission coinbas3.com replacement coinbas4.com replacement coinbasr.com replacement coinbasse.com insertion coinbasz.com replacement coinbaxe.com replacement coinbaye.com replacement coinbaze.com replacement coinbsase.com insertion coinbse.com omission coinbsse.com replacement coinbvase.com insertion coinbwase.com insertion coinbwse.com replacement coinbyase.com insertion coinbyse.com replacement coinbzase.com insertion coinbzse.com replacement coingase.com replacement coingbase.com insertion coinhase.com replacement coinhbase.com insertion coinjbase.com insertion coinmbase.com insertion coinnase.com replacement coinsbase.com plural coinvase.com replacement coinvbase.com insertion coionbase.com insertion coiunbase.com insertion cojinbase.com insertion cojnbase.com replacement cokinbase.com insertion colinbase.com insertion conbase.com omission cooinbase.com insertion coonbase.com replacement copinbase.com insertion couinbase.com insertion counbase.com replacement cpoinbase.com insertion cvoinbase.com insertion cxoinbase.com insertion dcoinbase.com insertion doinbase.com replacement fcoinbase.com insertion foinbase.com replacement oinbase.com omission voinbase.com replacement xcoinbase.com insertion xoinbase.com replacement c-oinbase.com hyphenation c0oinbase.com insertion c9oinbase.com insertion cdoinbase.com insertion cfoinbase.com insertion cioinbase.com insertion ckoinbase.com insertion cloinbase.com insertion co-inbase.com hyphenation co0inbase.com insertion co8inbase.com insertion

255 件中 100 件を表示

証拠および外部報告書

詳細な分析
Help & reporting

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

4 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およびドメイン 詐欺師が使用した(以下を含む) secure-help-com.zapier.app)
  • コミュニケーション — 詐欺師が使用したメール、テキストメッセージ、電話番号、ユーザー名

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

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

  • 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/secure-help-com.zapier.app"
  title="PhishDestroy threat report for secure-help-com.zapier.app"
  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>