跳转到安全报告
域安全和威胁情报
ammyield.com favicon

ammyield.com

注册商
Gname
PhishDestroy assessment 关键
可用性 内容不可用 最新观察中的内容不可用 观察到 · HTTP probe
病毒检测总数:11/89 Spamhaus DBL: DBL_PHISH 存储的阻止列表匹配项:2 自动品牌标签:MetaMask
OTX: 2 refs 2026年9月2日
API
该域名已被标记为恶意域名
安全引擎报告检测:11。 报告匹配的公共黑名单:2。 请格外小心——不要输入凭据或个人信息。
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
报告概览

冒充 MetaMask: ammyield.com — 内容不可用. 证据摘要: VirusTotal 11/89 (alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker); Spamhaus DBL_PHISH; 2 external…

为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。

Source evidenceVirusTotal 11 / 89 · OTX 2 references 5 sources

VirusTotal

11 / 89 engine detections

打开报告

Spamhaus DBL

DBL_PHISH

Google Safe Browsing

No threat flag

打开报告

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

Analysis

关键
VirusTotal
11 / 89
OTX
2 community refs

PhishDestroy threat report

Overview

ammyield.com is an impersonation phishing site. Its name borrows the language of automated market makers and yield farming, which suggests it was pitched at crypto users chasing DeFi returns. PhishDestroy first flagged it on 2026-09-02. The site has been offline since 2026-09-13 and was still unreachable when last checked on 2026-10-19.

How the scam works

Impersonation pages like this copy the look and wording of a legitimate crypto service so that visitors believe they are on the real platform. The visitor is usually asked to connect a wallet, sign a transaction or type in a recovery phrase to claim rewards, stake tokens or fix a supposed account problem. Each of these steps hands control to the operator. A signed approval lets them move tokens. A recovery phrase gives them the entire wallet. Either way, losses are typically immediate and cannot be reversed on-chain.

Evidence

Wallet-security lists took this domain seriously. MetaMask and the SEAL blocklist both carry it alongside PhishDestroy, and Spamhaus lists it in its domain blocklist under the phishing category. On VirusTotal, 11 of 89 engines flagged it as of 2026-09-13, including BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, G-Data, Gridinsoft, CRDF and alphaMountain.ai. That is a modest share of engines, but the vendors are independent of one another, and the domain also appears in two AlienVault OTX threat pulses.

Infrastructure

The domain was registered through Gname.com Pte. Ltd. It went dark on 2026-09-13, about eleven days after PhishDestroy first detected it. That short lifespan is typical of throwaway phishing domains, which are dropped once blocklists catch up and replaced with fresh names carrying the same branding.

What to do

If you connected a wallet to ammyield.com, use a token-approval checker to revoke any permissions you granted, and move your remaining assets to a fresh wallet if you are unsure what you signed. If you entered a seed phrase or private key, treat that wallet as fully compromised and transfer everything to a new wallet created from a new phrase straight away. Expect follow-up messages offering "recovery" help, and ignore them. Security teams should block the domain and watch for similarly named yield or AMM lookalikes registered through the same channels.

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask 已列入 View source
PhishDestroy PhishDestroy list View source
SEAL 已列入 View source

Last checked

Domain details

域名
OTX tags 2026-09all-domainsblocklistcrypto域名drainerfraudmonthlyphishdestroyphishingscam
注册商 Gname SG(SG)
ICANN 注册管理机构ICANN Lookup (RDAP) →
首次不可用所需时间 10 days
统计口径 从第一个存储的滥用报告到第一次观察到内容不可用所经过的时间。这并不能确定原因。
每份报告包含哪些内容 存储的传出报告记录可以参考当时可用的证据,例如供应商判决、注册数据、托管详细信息、分类或屏幕截图。此页面无法推断收件人交付、接收、确认或操作的确切有效负载。
技术详情Provenance & timestamps
首次发现2026年9月2日
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

域名服务器 1

  • patrick.ns.cloudflare.com
举报此域名 提交证据,帮助保护他人

VirusTotal 分析

11 / 89 安全供应商标记了该域
View on VT
Last analyzed First positive detection Previous stored snapshot: 4 detections
alphaMountain.ai
BitDefender
CRDF
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
SOCRadar
Sophos
VIPRE
Registration & observation details1

Availability observations

Last reachable observation

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.

ammyield.com
已保存的结果
无法访问
Stored observation history3

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

    不可用→可访问

  2. VirusTotal · Detection count

    4→11

  3. Availability monitor · Recorded state

    可访问→不可用

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. AlienVault OTX

    2 community references

    View source
  3. VirusTotal

    11/89 engine detections

    View source
  4. Added to PhishDestroy

    ammyield.com

    View source

仿冒域名

已存储 79 个仿冒域名

显示全部(67)
metasmask.io insertion 内部报告 metramask.io insertion 内部报告 mewtamask.io insertion 内部报告 mmetamask.io homoglyph 内部报告 mtamask.io omission 内部报告 mwetamask.io insertion 内部报告 nmetamask.io homoglyph 内部报告 metamark.io bitsquatting 内部报告 metamaskj.io addition 内部报告 metammask.io homoglyph 内部报告 metamnask.io homoglyph 内部报告 emtamask.io transposition m-etamask.io hyphenation meamask.io omission meatmask.io transposition meramask.io replacement mertamask.io insertion metaamask.io repetition metaamsk.io transposition metaask.io omission metalmask.io insertion metamaask.io insertion metamadsk.io insertion metamaek.io replacement metamak.io omission metamas.io omission metamasak.io insertion metamasdk.io insertion metamask-io.com various metamasl.io replacement metamasm.io replacement metamsak.io transposition metamsk.io omission metamusk.io vowel-swap metamzsk.io replacement metarnask.io homoglyph metmaask.io transposition metmask.io omission metsamask.io insertion metsmask.io replacement mettamask.io repetition metwmask.io replacement metyamask.io insertion metzmask.io replacement meyamask.io replacement meytamask.io insertion mitamask.io vowel-swap mnetamask.io homoglyph mretamask.io insertion mrtamask.io replacement mstamask.io replacement mteamask.io transposition mwtamask.io replacement rnetamask.io homoglyph matamask.io bitsquatting mdtamask.io bitsquatting metamasi.io bitsquatting metamasj.io bitsquatting metamaska.io addition metamaskk.io addition metamaskl.io addition metamaso.io bitsquatting metamesk.io bitsquatting metamqsk.io bitsquatting metemask.io bitsquatting netamask.io homoglyph xn--metamas-bhb.io homoglyph

证据与外部报告

深度分析
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 账户,以及任何使用同一密码的账户
  • 启用双因素认证 使用身份验证器应用(而非短信)。禁用基于短信的恢复功能
  • 冻结卡片 如果您在钓鱼网站上输入了银行信息

我应该为报告收集哪些信息?

联邦调查局(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.
  • 确切日期和时间 — 每笔交易的详情以及与诈骗者的首次接触
  • 屏幕截图 — 诈骗网站、聊天消息、电子邮件、钱包交易、社交媒体
  • 所有网址和域名 诈骗者使用的(包括 ammyield.com)
  • 通信 — 诈骗者使用的电子邮件、短信、电话号码、用户名

即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。

我应该向哪里举报这起诈骗?

  • 联邦调查局(FBI)IC3 — 互联网犯罪投诉中心(美国联邦举报渠道)
  • 欧洲刑警组织 — 欧洲网络犯罪报告(欧盟)
  • 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?

  • 虚假网站 — 与正规网站完全一致的克隆网站,仅域名略有改动
  • 猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任,随后钱被骗走
  • 退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • 利用人工智能实施的诈骗 — 深度伪造、自动化网络钓鱼以及人工智能生成的网站,使得欺诈行为更难被察觉

将来我该如何保护自己?

  • 将官方网站添加到书签 — 切勿点击来自电子邮件、私信或广告中的链接
  • 验证域名 — 查看 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/zh/embed/domain/ammyield.com"
  title="PhishDestroy threat report for ammyield.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>