VirusTotal
4 / 92 engine detections
打开报告“honeylink.cc — агрегатор ресурсов”
冒充 Kraken: honeylink.cc — 最后已知的活跃状态 (HTTP 200). 证据摘要: VirusTotal 4/92 (alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet, Webroot); Spamhaus DBL_SPAM…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
4 / 92 engine detections
打开报告DBL_SPAM
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
The domain honeylink.cc appeared on the PhishDestroy blocklist on 2026-10-19. No clear brand or service is impersonated, but the timing and detection pattern suggest it is aimed at cryptocurrency users. PhishDestroy’s first observation records the site status as unknown as of the same date. The domain is therefore treated as a potential phishing or wallet‑draining portal.
Typical operations for a site of this type involve presenting a fake login or wallet‑connection page that asks visitors for private keys, seed phrases, or to approve blockchain transactions. When a victim supplies credentials or authorizes a transaction, the attacker can move the funds to an address they control. The loss is usually the entire balance of the compromised wallet, as the attacker can instantly drain it once approval is granted.
VirusTotal scanned honeylink.cc on 2026-10-19 and returned four positive detections out of ninety‑two engines. The flagging vendors are alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet and Webroot, all of which label the site as malicious. The domain is also listed on the PhishDestroy blocklist. No additional detections from Google Safe Browsing, urlscan.io, or Spamhaus are recorded at this time.
The domain was registered on 2026-06-26 through Cloudflare, Inc., giving it roughly four months of existence before being flagged. Hosting resolves to the IP address 172.67.219.72, which belongs to Cloudflare’s global content‑delivery network, indicating the operators are using a reputable CDN to mask the origin server. No specific TLS issuer information is available beyond the standard Cloudflare certificate.
Anyone who entered wallet credentials, private keys, or approved transactions on honeylink.cc should immediately change all related passwords, enable strong two‑factor authentication, and revoke any blockchain approvals granted to unknown addresses. Monitor wallet activity for unauthorized transfers and consider moving remaining funds to a new, secure wallet. Security teams should block honeylink.cc at the DNS and proxy layers, add the domain to internal blocklists, and watch for newly registered domains using the same registrar or hosting provider that exhibit similar malicious patterns.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/+6IUKIYdACOE1OTBkStored page referencehttps://t.me/+sBEeeNX_0pQzNDE6Stored page referencehttps://t.me/MmoparanoidStored page referencehttps://t.me/SlimeChange_botStored page referencehttps://t.me/ashoo_comStored page referencehttps://t.me/black156botStored page referencehttps://t.me/honeylink1_botStored page referencehttps://t.me/honeylinksupStored page referencehttps://t.me/nv_6_botStored page referencehttps://t.me/omglinkStored page referencehttps://t.me/rocket_btc_botStored page referencehttps://t.me/zeleniymir420botStored page referenceIoC extraction recorded 2026-10-20 04:00:09 UTC
Edge-IP 声誉不属于此域。
hunts.ns.cloudflare.comophelia.ns.cloudflare.comLocation describes the IP network.
c63459fd317fd3d544d7aacb6d91ae8f33fcaeebc1fe7046e75f2ef57b99da4fSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of honeylink.cc · checked Oct 19, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
https://honeylink.cc/Content-Type: text/html; charset=utf-8X-Powered-By: ExpressCache-Control: public, max-age=0, s-maxage=60, stale-while-revalidate=120CF-Cache-Status: EXPIREDContent-Encoding: gzipServer: cloudflare7f456bb9bdd04b45c80aef0f2bb64c7d33e86df720a1a714d3ae73f827b94dach3=":443"; ma=86400public, max-age=0, s-maxage=60, stale-while-revalidate=120EXPIREDa4cfc505b9f5141d-FRAkeep-alivegziptext/html; charset=utf-8Mon, 19 Oct 2026 12:26:10 GMT{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=PL0v5ibR1cQiB8HP8ieLvIvTxGjeDITnTgG44CkJiXyN0G4WTiXVH%2BBuIZ2NiR9vNWwQ5GZf1L%2BXHoSZvUa8JmxRYBsXQt%2Be7XSKsQBrSPNLpwzdyFQ3wNJgZWvQZhk%3D"}]}cloudflarechunkedExpressValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→live_content
content_served
可访问
Page captured
View sourceNo threat flag
View source4/92 engine detections
View sourcehoneylink.cc
View source已存储 114 个仿冒域名
显示 114 个中的 100 个
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
honeylink.cc
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 ↗
honeylink.cc)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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
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.