VirusTotal
4 / 91 engine detections
打开报告“Pieni hetki...”
被列入黑名单的域名: claim.gobob.network — 隐形 · 可达 (HTTP 403). 证据摘要: VirusTotal 4/91 (ChainPatrol, Chong Lua Dao, Gridinsoft, SOCRadar); cloaking observed; PhishDestroy…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
4 / 91 engine detections
打开报告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
This domain, claim.gobob.network, is currently flagged as a high-risk crypto drainer operation. Analysis indicates the site is still active as of July 12, 2026, despite returning an HTTP 403 status, which may suggest restricted access or backend filtering mechanisms in place. The page title, 'Pieni hetki...', does not correspond to any known legitimate service, and no brand or platform is explicitly named in available intelligence. The domain resolves to IP address 188.114.96.3, hosted on AS13335 under Cloudflare, Inc., a common infrastructure choice for threat actors seeking anonymity and DDoS protection. Infrastructure analysis reveals the use of Cloudflare and HTTP/3, alongside Cloudflare Browser Insights, which may be employed to monitor visitor behavior or evade detection. The SSL certificate is issued by Google Trust Services, specifically the WE1 intermediate, which is not inherently malicious but is frequently used in both legitimate and malicious contexts. The domain appears on one security blocklist, and three out of ninety-five security vendors on VirusTotal have flagged it as malicious, though the absence of broader detection does not confirm safety. The Gridinsoft trust score of 0/100 further supports the assessment of high risk. What remains uncertain is the exact mechanism of the crypto drainer, as the page content has not been directly analyzed. The HTTP 403 response may indicate the site is selectively serving malicious payloads or is in a transitional state. Defenders should treat this domain as an active threat, particularly in environments where cryptocurrency transactions occur. Network-level blocking of 188.114.96.3 and monitoring for connections to claim.gobob.network are recommended. If internal logs show prior visits to this domain, endpoint analysis should be conducted to identify potential wallet compromise or unauthorized transactions. No further brand or platform attribution is available at this time.
For the registrable domain gobob.network 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.
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.
Edge-IP 声誉不属于此域。
Location describes the IP network.
507c4208189175c9c4c9347e2d9eac8dbd38bb63d372948b0b2113a972e0fd8agobob.networkSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
status_split · cloudflare_challenge: raw=cf_challenge; http=403; via=https_proxy; server=cloudflare
claim.gobob.network
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
未知→protected
cloudflare_challenge · Cloudflare · challenge
不可用→可访问
https://radar.cloudflare.com/scan/1e4b3962-ee76-4653-a324-48519cb4c69a
可访问→不可用
可访问→不可用
No threat flag
View source4/91 engine detections
View sourceclaim.gobob.network
View sourcePage captured
View source由 1 名社区成员报告;首次发现于 2025年11月20日
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 ↗
claim.gobob.network)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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.