VirusTotal
3 / 91 engine detections
打开报告myatomicwallet.readme.io:冒充 Atomic Wallet,PhishDestroy 于 2026-09-17 检测到。风险:关键(71/100)。注册商:1API。状态:最后已知的活跃状态。托管:Cloudflare, Inc。VirusTotal:3/91 个引擎标记。请勿输入登录凭据,也不要连接钱包。
“myatomicwallet”
冒充 Atomic Wallet: myatomicwallet.readme.io — 最后已知的活跃状态 (HTTP 302). 证据摘要: VirusTotal 3/91 (CRDF, Forcepoint ThreatSeeker, VIPRE); PhishDestroy score 71/100.…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
3 / 91 engine detections
打开报告无社区引用
打开报告provider verdict: clean
打开报告无威胁标记
打开报告结果反映各来源的采集时间。零检出不代表安全。OTX 引用为社区发布的内容。
PhishDestroy threat report
myatomicwallet.readme.io is a phishing page that impersonates Atomic Wallet, the non-custodial multi-coin crypto wallet. It runs on a subdomain of ReadMe, a documentation-hosting service, so the address borrows a legitimate parent domain while presenting itself under the page title "myatomicwallet". PhishDestroy first flagged it on 2026-09-17. As of 2026-10-19 the site was still alive and redirecting visitors elsewhere.
Atomic Wallet users hold their own keys, so there is no account password to steal. Pages like this one try to obtain the 12-word recovery phrase or private key instead, usually through fake "restore", "sync" or "support" prompts, or they push a counterfeit wallet download. Once the phrase is entered, the attacker can rebuild the wallet on their own device and move every asset out. These transfers cannot be reversed. The redirect means the readme.io address works as a disposable front door that forwards victims to wherever the operator currently hosts the lure.
Independent detection is thin. On 2026-10-01 only 3 of 91 VirusTotal engines flagged the address: CRDF, Forcepoint ThreatSeeker and VIPRE. PhishDestroy is the only blocklist carrying it so far. Most browsers and security tools will therefore not warn a visitor. The classification rests on the brand impersonation itself, not on vendor consensus.
The address resolves to 104.16.241.118 on Cloudflare's network, geolocated to Canada. That is the edge serving the ReadMe platform, not hardware the operator controls. Free subdomains on reputable documentation services are popular with phishers because they inherit the parent domain's reputation and cost nothing to replace when one is taken down. The operator never had to register a domain at all.
If you typed your Atomic Wallet recovery phrase or private key anywhere after landing here, treat the wallet as compromised. Create a new wallet with a fresh phrase on a device you trust, and move any remaining funds to it immediately. If you installed software from this page, uninstall it, scan the device, and assume any wallet on that machine is exposed. Atomic Wallet never asks for your phrase through a website, and real support staff will never request it. Defenders should block the full subdomain, watch for other Atomic-themed subdomains on ReadMe and similar documentation hosts, and report the page to ReadMe for removal.
已存档的页面、网络和扫描器观测结果,按来源和观测时间分组。
观察到: · Retrieved:
| Uuid | 585876de-3a78-40c1-a4cf-76ebed064bb7 |
|---|---|
| Final url | https://myatomicwallet.readme.io/inactive |
| 状态 | 401 |
| 已重定向 | same-domain |
| History | [
{
"url": "https://myatomicwallet.readme.io/",
"status": 302
},
{
"url": "https://myatomicwallet.readme.io/inactive",
"status": 401
}
] |
| DOM structure hash | 98320ca057e84299166cc9c91b98206dd50ca6f5f7a2a1b2d2100fe21149f845 |
| Document hash | 40df1a0285aa4d836ce8dc1ecf519178f0be9196c8d96a2705de2e0fc4c803e0 |
| Radar rank | {
"bucket": ">200000"
} |
| DNS 记录 | [
{
"name": "cdn.readme.io",
"type": "CNAME",
"value": "ssl.readmessl.com"
},
{
"name": "cdn.readme.io",
"type": "CNAME",
"value": "ssl.readmessl.com"
},
{
"name": "myatomicwallet.readme.io",
"type": "CNAME",
"value": "cname.readmessl.com"
},
{
"name": "myatomicwallet.readme.io",
"type": "CNAME",
"value": "cname.readmessl.com"
}
] |
| DNSSEC 有效 | false |
| Ip | 104.16.241.118 |
| 注册记录 | {
"registrar": "1API GmbH",
"created": "2011-05-17T10:06:31Z",
"updated": "2026-08-12T10:17:07Z",
"expires": "2027-05-17T10:06:31Z",
"nameservers": [
"uma.ns.cloudflare.com",
"jeremy.ns.cloudflare.com"
]
} |
观察到: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 52,
"malicious": 3,
"suspicious": 0,
"undetected": 37
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"VIPRE": "malware",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| 注册商 | 1API GmbH |
| 创建 | 2011-05-17T10:06:31Z |
| Expires | 2027-05-17T10:06:31Z |
| Updated | 2026-08-12T10:17:07Z |
| 首次发现 | 2026-09-12T10:25:54Z |
| DNS 记录 | [
{
"ttl": 98,
"type": "CAA",
"value": "pki.goog;"
},
{
"ttl": 120,
"type": "CNAME",
"value": "cname.readmessl.com"
},
{
"ttl": 98,
"type": "CAA",
"value": "comodoca.com"
},
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700::6810:f176"
},
{
"ttl": 98,
"type": "CAA",
"value": "letsencrypt.org"
},
{
"ttl": 98,
"type": "CAA",
"value": "ssl.com"
},
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700::6810:f276"
},
{
"ttl": 98,
"type": "CAA",
"value": "pki.goog;"
},
{
"ttl": 98,
"type": "CAA",
"value": "digicert.com"
},
{
"ttl": 300,
"type": "A",
"value": "104.16.241.118"
},
{
"ttl": 98,
"type": "CAA",
"value": "letsencrypt.org"
},
{
"ttl": 300,
"type": "A",
"value": "104.16.242.118"
},
{
"ttl": 98,
"type": "CAA",
"value": "digicert.com"
},
{
"ttl": 98,
"type": "CAA",
"value": "comodoca.com"
},
{
"ttl": 98,
"type": "CAA",
"value": "ssl.com"
}
] |
| Dns at | 2026-10-21T11:30:27Z |
| Jarm | 27d27d27d00027d00042d43d00041df04c41293ba84f6efe3a613b22f983e6 |
| Certificate | {
"san": [
"readme.io",
"*.readme.io"
],
"issuer": "Google Trust Services / WE1",
"serial": "3b6df4b000c463020e342c94488fa3a1",
"sha256": "52054a9ca28442ddb0ee75f981b79aebecbf2e9ee1749e6243e6439680556ef5",
"subject": "readme.io",
"valid_to": "2026-12-07T17:48:12Z",
"valid_from": "2026-09-08T16:48:24Z"
} |
| 注册记录 | {
"registrar": "1API GmbH",
"registrar_iana_id": "1387",
"registrar_url": "http://www.1api.net",
"created": "2011-05-17T10:06:31Z",
"updated": "2026-08-12T10:17:07Z",
"expires": "2027-05-17T10:06:31Z",
"status": [
"clientTransferProhibited"
],
"nameservers": [
"jeremy.ns.cloudflare.com",
"uma.ns.cloudflare.com"
],
"dnssec": "unsigned"
} |
不是。PhishDestroy 将 myatomicwallet.readme.io 归类为“冒充 Atomic Wallet”(风险:关键,71/100),首次检测于 2026-09-17。VirusTotal:3/91 个引擎标记。请将该网站视为不安全。
不安全。请勿在 myatomicwallet.readme.io 连接钱包、签署消息或批准代币。钓鱼网站会请求授权(approve、setApprovalForAll、Permit2),让运营者转走你的资产,而已确认的交易无法撤销。
更改你在该网站输入过的所有密码,并开启双重验证。如果你连接过钱包或签署过任何内容,请撤销授权,并将剩余资金转到新钱包;切勿透露助记词。分步指南:紧急处理指南。
Edge-IP 声誉不属于此域。
jeremy.ns.cloudflare.comuma.ns.cloudflare.com位置信息描述的是 IP 网络。
52054a9ca28442ddb0ee75f981b79aebecbf2e9ee1749e6243e6439680556ef5readme.io已保存的证书元数据。未带时区的证书日期按存档原样显示。传输加密并不能证明该网站值得信任。
Google PageSpeed Insights — 移动端性能审核: myatomicwallet.readme.io · checked Sep 25, 2026
估算时间描述的是一个观测时间窗口。它并不能证明注册商采取了措施,也不代表网站变为不可访问的确切时刻。
比较浏览器与爬虫各自收到的内容,并检查是否存在 Keitaro 流量分发。
myatomicwallet.readme.io
由监测程序和来源采集器保留的带日期变更记录。最新观测排在最前;来源状态并不能证明站点已被下架。
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→redirected
http_redirect
未知→redirected
http_redirect
redirected
http_redirect
1→2
可访问
列入名单的域名至少会收到一份滥用举报;此条目没有保留的通知记录。
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
Template-based draft · optional AI wording assistance requires separate consent
请根据您提供过的信息选择相应的步骤。请将本报告的副本与您自己的记录一并保存。
停止使用可疑网站。请通过官方应用或您已信任的网址访问真正的服务。
请将原始邮件、收据、消息和截图保存在安全的地方。基于事实的时间线有助于受理机构了解事件经过。 IC3 evidence guidance ↗
myatomicwallet.readme.io)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
举报并不能保证追回损失或启动调查,但及时、准确的交易数据可以帮助执法机构和服务提供商追踪事件。
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
本报告汇总了已保存的页面快照、注册与网络记录、扫描器结果以及 PhishDestroy 举报历史。每个来源均保留各自的观测日期。打开来源报告即可查看原始结果。
AI 辅助分析的撰写时间: 。该分析描述的是当时可获得的证据;之后的来源核查结果可能有所变化。
快照记录的是当时显示的内容。扫描器结果记录的是该服务商在检查时的评估。有效证书或零检出结果都不能保证安全。