VirusTotal
4 / 91 engine detections
打开报告“PublicNode”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@hetzner.com.
The latest stored availability evidence still shows the domain reachable; 5 months has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
冒充 Scroll: rpc.534351.scroll.chain.cooking — 最后已知的活跃状态 (HTTP 301). 证据摘要: VirusTotal 4/91 (ChainPatrol, Chong Lua Dao, Gridinsoft, Seclookup); URLQuery 3…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
4 / 91 engine detections
打开报告3 threat-system alerts
打开报告5/14
checked — no match recorded
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.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Hagezi Threat Feed | rpc.534351.scroll.chain.cooking |
malicious | Sinkholed |
| DNS4EU | rpc.534351.scroll.chain.cooking |
malicious | Sinkholed |
| Quad9 DNS | rpc.534351.scroll.chain.cooking |
malicious | Sinkholed |
PhishDestroy threat report
PhishDestroy identifies an active crypto drainer domain impersonating the Scroll brand, specifically targeting users through deceptive RPC endpoints. The domain rpc.534351.scroll.chain.cooking mimics legitimate Scroll infrastructure to trick users into connecting wallets or signing malicious transactions. This campaign leverages false associations with Scroll’s branding to exploit trust in the ecosystem, posing a direct financial threat to cryptocurrency holders. This domain was flagged by 2 security blocklists and is currently blocked by MetaMask and SEAL. The domain resolves to IP 157.180.21.170 and was registered on February 05, 2025, through Cloudflare, Inc. The SSL certificate is issued by Let’s Encrypt, which is commonly abused in phishing campaigns due to its automated issuance process. On VirusTotal, only 2 out of 95 security vendors flagged this domain as malicious at the time of analysis, indicating a low detection rate among automated tools. Users who visited or interacted with this domain should immediately disconnect their wallets, revoke any unauthorized connections via tools like Revoke.cash, and scan their devices for malware. If transactions were signed, monitor for unauthorized transfers and report suspicious activity to Scroll’s official support channels. Always verify domains by cross-referencing official Scroll documentation or using PhishDestroy’s verification tools before engaging.
For the registrable domain chain.cooking 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 声誉不属于此域。
annalise.ns.cloudflare.comcarl.ns.cloudflare.comLocation describes the IP network.
c361c3108d5e787a4fb4016e9dd1f0730df77f28dcea4639104de68bd32a5900Saved 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.
redirect: raw=redirect_301; http=301; via=http_proxy; location=https://rpc.534351.scroll.chain.cooking/
rpc.534351.scroll.chain.cooking
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→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
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
不可用→可访问
不可用→可访问
可访问→不可用
不可用→可访问
可访问→不可用
No threat flag
View source4/91 engine detections
View sourcerpc.534351.scroll.chain.cooking
View sourcePD-20260506-BE130B
由 1 名社区成员报告;首次发现于 2026年5月6日
PD-20260506-BE130B Recipient: abuse@hetzner.com Policy Violations: Illegal Activities: Active phishing operation targeting victims Fraud & Deception: Impersonation of legitimate services Identity Theft: Collection of credentials under false pretenses Applicable Laws (US): 18 U.S.C. § 1343 - Wire Fraud 18 U.S.C. § 1030 - Computer Fraud and Abuse Act (CFAA) 15 U.S.C. § 45 - FTC Act (Deceptive Practices) Federal laws prohibit wire fraud, computer fraud, and deceptive business practices. Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
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 ↗
rpc.534351.scroll.chain.cooking)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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.