VirusTotal
11 / 89 engine detections
فتح التقرير
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@pir.org.
The latest stored availability evidence still shows the domain reachable; 1 month 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.
انتحال MetaMask: chain-account.org — يمكن الوصول إليها · الوصول مقيد (HTTP 403). ملخص الأدلة: VirusTotal 11/89 (ChainPatrol, BitDefender, CRDF, Forcepoint…
يبقى تحليل PhishDestroy AI المفصل أدناه باللغة الإنجليزية للحفاظ على السجل الجنائي الرقمي الأصلي.
11 / 89 engine detections
فتح التقرير2 threat-system alerts
فتح التقرير15/100
فتح التقرير4 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
chain-account.org is an impersonation phishing site built to pass as a legitimate crypto account service. Its listing on the MetaMask and SEAL blocklists points squarely at wallet holders. PhishDestroy first caught it on 2026-09-11, and it went offline the next day, 2026-09-12. As of 2026-10-19 the site is dead and its content is blocked by the provider.
Impersonation pages like this copy the look and wording of a trusted crypto service, then ask the visitor to log in, verify an account or connect a wallet. Whatever the victim hands over, whether a seed phrase, a private key or a signed transaction approval, gives the operators control of the funds it guards. The page title showed only a generic "Loading…" placeholder rather than a branded name, while our classification is impersonation phishing.
Eleven of 89 VirusTotal engines flagged the domain by 2026-09-14. They include crypto-focused ChainPatrol alongside BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft and Kaspersky. Independent listings by MetaMask and SEAL, both centred on Web3 fraud, back the PhishDestroy verdict. The domain also appears in four AlienVault OTX threat pulses, so other researchers tracked it too.
The domain was registered on 2026-09-06 through Fewmoretaps OU d/b/a Trustname.com, only five days before PhishDestroy detected it. That short gap is typical of throwaway phishing domains spun up for a brief campaign. Traffic ran through Cloudflare's network in the US, which hides the real origin server behind a shared proxy address.
If you typed a seed phrase or private key into this site, treat that wallet as compromised. Move any remaining assets to a new wallet created on a clean device. If you connected a wallet or signed anything, review and revoke token approvals with a trusted approval checker, and watch for unexpected outgoing transfers. Any password you reused there should be changed, with 2FA enabled on the real service. Security teams should block chain-account.org at DNS and proxy level, search logs for past visits, and warn users that legitimate wallet providers never ask for a recovery phrase.
Last checked
لا تُنسب سمعة Edge-IP إلى هذا المجال.
colin.ns.cloudflare.comryleigh.ns.cloudflare.comLocation describes the IP network.
7339fdde40634d0f0664346345b8ce09af26b9458beeca328d85687b27c1094eSaved 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 chain-account.org · checked Sep 11, 2026
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.
chain-account.org
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير معروف→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
غير متوفر→يمكن الوصول إليه
يمكن الوصول إليه→غير متوفر
يمكن الوصول إليه
No threat flag
View source11/89 engine detections
View source4 community references
View sourcePD-20260911-24B5E9
chain-account.org
View sourcePage captured
View source٧٩ نطاقًا متشابهًا محفوظًا
PD-20260911-24B5E9 Recipient: abuse@pir.org 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 ↗
chain-account.org)حتى لو لم تكن جميع التفاصيل متوفرة — تقديم بلاغ على أي حال. فحتى المعلومات الجزئية تساعد في التحقيقات.
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
تحليل التهديدات باستخدام قائمة الحظر المخزنة، وWHOIS، وDNS، وأدلة الفحص العامة
امسح الآنأرسل النطاقات المشبوهة إلى قاعدة بيانات التهديدات الخاصة بنا — ساهم في حماية المجتمع
إبلاغتقارير التصيد الاحتيالي الأخيرة وتغييرات التوفر الملحوظة
مراقبةراقب التهديدات في الوقت الفعلي أو اعترض على هذا الإدراج إذا كنت تعتقد أنه إنذار كاذب
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.