跳转到安全报告
⚠️
该域名已被标记为恶意域名
安全引擎报告检测:6。 报告匹配的公共黑名单:2。 请格外小心——不要输入凭据或个人信息。
域安全和威胁情报

purecoder[.]io

“PureCoder Tools | Windows Desktop App Developer”

威胁判定 关键 90/100 证据评分
可用性 最后已知的活跃状态 最新存储的可达性观察
病毒检测总数:6/91 存储的阻止列表匹配项:2 品牌冒充:Telegram 最后已知的活跃状态
OTX: 2 refs 2026年8月9日 Telegram CDN
证据摘要
重要
评分
90/100

Assessment
Stored evidence for purecoder.io: VirusTotal recorded 6 detections among 91 scanners on 2026-08-09. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for purecoder.io. Each item in this report remains at the scope supplied by its dated source record.

Detection Evidence
VirusTotal records 6 detections among 91 scanners in the stored snapshot dated 2026-08-09. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-08-09 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.

Source Context
MetaMask and SEAL are recorded as named external blocklist observations for purecoder.io in the snapshot dated 2026-08-09. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains purecoder.io as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.

Reachability and Timeline
The record first observed purecoder.io on 2026-08-09. The MetaMask and SEAL blocklist snapshot is dated 2026-08-09 and remains a separate event in the stored timeline. The registration date is separately recorded as 2022-03-07. A URLScan reference was stored on 2026-08-09 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.

Registration and Infrastructure
The record lists NICENIC INTERNATIONAL GROUP CO., LIMITED as the registrar for purecoder.io. The source stores 104.21.81.171 as the observed address for purecoder.io. The registration date for purecoder.io is recorded as 2022-03-07. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.

Conclusion
The purecoder.io record states that VirusTotal recorded 6 detections among 91 scanners on 2026-08-09. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-08-09. PhishDestroy remains a separate publisher catalogue entry in the stored record. NICENIC INTERNATIONAL GROUP CO., LIMITED is presented only as the recorded registrar, while 104.21.81.171 is presented only as the observed address. The supported conclusion is bounded to the exact stored observations for purecoder.io. Any statement beyond those source values would require additional dated material.

Recommended Actions
Use a known service address obtained separately from this report and avoid submitting sensitive information to purecoder.io during review. Defenders can retain the exact purecoder.io hostname as an indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to purecoder.io; the stored record does not justify extending that rule to 104.21.81.171 or the NICENIC INTERNATIONAL GROUP CO., LIMITED registrar record.

VirusTotal
VirusTotal
6 det.
OTX references
TLS 证书
Google Trust Services
年龄
4.4 yr
观测状态
最后已知的活跃状态
PhishDestroy
DestroyList
已列入
数据覆盖范围 VirusTotal 6 / 91 URLQuery 未检查 PhishStats 未检查 OTX 2 community references CF雷达 scan completed URLScan capture 存储的报告 URLScan verdict 分析完成 DNS 阻断 未检查 TLS valid certificate, 44d WHOIS 54 mo old 屏幕截图 4 captures · 3 sources 重定向链 未探查
网络安全情报 Registrar context
Registrar context NiceNIC
Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
NiceNIC Verdict Full Investigation

威胁响应 Pipeline

发现
Checks
Reports
可用性
17/18

阻止列表覆盖

10 个来源 · 于 2026年8月9日 同步

检测时间线

按时间顺序显示已存储的观测记录。

  1. 已存储的观测记录

    已存储的观测记录:首次观测为 alive

金融基础设施

地址提取自网络钓鱼页面。

已保存的截图

域名情报

域名
URLScan Verdict 分析完成 score 0 report ↗
服务器 / ASN cloudflare · AS13335 Cloudflare, Inc.
IP Context Cloudflare shared edge origin IP hidden Edge-IP 声誉不属于此域。
注册商 NiceNIC RU(RU) PhishDestroy Investigation
IP 地址 104.21.81.171 CDN
地理位置CA Toronto, CA
网络AS13335 · Cloudflare, Inc.
源 IP 隐藏在 CDN 代理后面。边缘地址的反向 IP 结果包含不相关的租户;查找源头需要被动 DNS 或证书透明数据。
注册信息创建 2022年3月7日 Expires 2027年3月7日
技术详情DNS、SSL SAN、时间戳
首次发现2026年8月9日
DOM Analysisanalyzed 2026年8月9日score 90/1001 brand signal
Submitted URLhttp://purecoder.io/
域名服务器anahi.ns.cloudflare.comandy.ns.cloudflare.com
Favicon Hash
页面标题
PureCoder Tools | Windows Desktop App Developer
Impersonates
Telegram
TLS 证书
Valid transport encryption · 颁发者 Google Trust Services · valid for 44 days

技术

识别出 2 项高置信度技术

Cloudflare HTTP/3
Cloudflare Radar
举报此域名 提交证据,帮助保护他人

VirusTotal 分析

6 / 91 安全供应商标记了该域
View on VT
Last analyzed
alphaMountain.ai
Bfore.Ai PreCrime
Dr.Web
Fortinet
Gridinsoft
SOCRadar

存档证据

Wayback Machine Snapshot
历史快照可供证据审查
View Archive
网站性能分析

Google PageSpeed Insights — mobile performance audit of purecoder.io · checked Aug 9, 2026

88
Needs Work
Performance
FCP
3.04s
First Contentful Paint
LCP
3.04s
Largest Contentful Paint
CLS
0.007
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
3.12s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
网站配置分析
Stored observations are retained with their original collection time.
robots.txt Present · HTTP 200
/description/ /guide/ /assets/
Sitemap 1 page · HTTP 200

您是否受到本网站的影响?

If credentials were compromised, report immediately. Do not engage with recovery scammers.

如果您与此域交互、输入个人信息或连接加密货币钱包,请立即采取行动。以下资源可帮助您报告事件并保护自己。

欧洲刑警组织
查找您所在欧盟国家/地区的官方报告渠道
National police directory
警惕“数据恢复”诈骗! 犯罪分子可能会冒充调查员、律师或追债员再次联系受害者。 请勿支付预付费用或共享凭证。 没有任何合法服务可以保证恢复被盗的加密货币。 了解有关康复欺诈的更多信息 →

向当地主管部门报告

选择您所在的国家/地区以获取 官方网络犯罪联系人创建投诉草稿 →

97个国家目录
AI辅助草稿——事件详细信息由AI提供商处理 自行审核并提交

检查任意域名

使用存储的阻止列表、WHOIS、DNS 和公共扫描证据进行威胁分析

立即扫描

举报网络钓鱼

将可疑域名提交至我们的威胁数据库——保护社区

报告

实时威胁动态

最近的网络钓鱼报告和观察到的可用性变化

监控

随时掌握最新信息,确保安全

请实时监控威胁,或者如果您认为这是误报,请对该条目提出异议

实时威胁动态 对该列表提出异议

针对受害者的建议与指导

据估计 $51 billion 于2024年流入非法加密货币钱包(source). 如果你曾与 purecoder.io — 立即行动。

我应该立即采取什么措施?
紧急
  • 撤销令牌授权 — use revoke.cash 撤销授予恶意智能合约的访问权限
  • 转移剩余资金 迁移到一个全新的钱包。该受损钱包已不再安全
  • 更改所有密码 — 电子邮件、Exchange 账户,以及任何使用同一密码的账户
  • 启用双因素认证 使用身份验证器应用(而非短信)。禁用基于短信的恢复功能
  • 冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息?
联邦调查局(FBI)指南

联邦调查局,其中最重要的细节是交易数据:

  • 加密货币地址 — 诈骗分子的钱包(例如, 0x5856...35985)
  • 金额及加密货币类型 — 确切金额(例如:1.02345 ETH、0.5 BTC、500 USDT)
  • 交易 ID(哈希值) — 唯一的区块链交易标识符
  • 确切日期和时间 — 每笔交易的详情以及与诈骗者的首次接触
  • 屏幕截图 — 诈骗网站、聊天消息、电子邮件、钱包交易、社交媒体
  • 所有网址和域名 诈骗者使用的(包括 purecoder.io)
  • 通信 — 诈骗者使用的电子邮件、短信、电话号码、用户名

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

我应该向哪里举报这起诈骗?
  • 联邦调查局(FBI)IC3 — 互联网犯罪投诉中心(美国联邦举报渠道)
  • 欧洲刑警组织 — 欧洲网络犯罪报告(欧盟)
  • Chainabuse — 在各交易所和平台上标记诈骗钱包
  • 您的加密货币交易所 — notify its fraud team immediately; it may be able to preserve records or restrict funds held on its platform
  • 当地警方 — 即使无法立即采取行动,也能留下正式记录

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

加密货币诈骗通常是如何运作的?
  • 虚假网站 — 与正规网站完全一致的克隆网站,仅域名略有改动
  • 恶意批准 — “连接钱包”的提示会使攻击者获得无限的代币消费权限
  • 猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任,随后钱被骗走
  • 退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • 虚假广告与空投 — 谷歌/社交媒体广告和“免费代币”优惠会导致钱包被掏空
  • 利用人工智能实施的诈骗 — 深度伪造、自动化网络钓鱼以及人工智能生成的网站,使得欺诈行为更难被察觉
将来我该如何保护自己?
  • 使用硬件钱包 (Ledger、Trezor)。切勿在浏览器钱包中存储大额资金
  • 将官方网站添加到书签 — 切勿点击来自电子邮件、私信或广告中的链接
  • 阅读每项批准 — 签名前请验证权限。拒绝无限制的批准
  • 验证域名 — 查看 PhishDestroy 在进行互动之前,请检查HTTPS、拼写和域名注册时间。
  • “好得令人难以置信”=骗局 — 保证收益、名人代言、紧迫的截止日期

外部工具

HTML · IFRAME

嵌入此报告

在您的网站或博客上分享此威胁情报

embed.html
<iframe
  src="https://phishdestroy.io/zh/embed/domain/purecoder.io"
  title="PhishDestroy threat report for purecoder.io"
  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>