VirusTotal
3 / 91 engine detections
Raporu aç“Welcome to NodeRestores”
BlockDAG taklidi: blockdaghelp.network — İçerik kullanılamıyor. Kanıt özeti: VirusTotal 3/91 (alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft); URLQuery…
Özgün adli kaydı korumak için aşağıdaki ayrıntılı PhishDestroy AI analizi İngilizce bırakılmıştır.
3 / 91 engine detections
Raporu aç1 threat-system alert
Raporu açSuspicious
Raporu aç3/14
checked — no match recorded
no community references
Raporu açNo threat flag
Raporu açNo malicious flag
Raporu açResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | blockdaghelp.network |
malicious | Sinkholed |
PhishDestroy threat report
Analysis as of July 22 2026 indicates that blockdaghelp.network is registered through Gname.com Pte. Ltd. on March 5 2026 and is currently taken offline. The domain resolves to IP 45.133.200.14, which is assigned to AS200313 (IT WEB LTD) in the Netherlands. DNS resolution shows the authoritative nameservers ns1.prohoster.name and ns2.prohoster.cc, and the MX record points to the domain itself (priority 0, host blockdaghelp.network), a configuration often observed in fraudulent mail setups. The web server presents an Nginx service behind a Cloudflare edge, and the page delivers JavaScript libraries from jsDelivr, cdnjs, and crypto‑js, all served over a Let’s Encrypt certificate issued under the R13 profile.
The page title returned by the HTTP response is “Welcome to NodeRestores”, which bears no obvious relation to the targeted brand BlockDAG, confirming the presence of brand impersonation. Gridinsoft assigns a trust score of 0 / 100, and the domain is listed on two security blocklists curated by PhishDestroy and ScamSniffer. VirusTotal analysis shows that 2 of 94 scanning engines flagged the domain, reinforcing the malicious classification. The combination of a newly created domain, low trust rating, mismatched page title, and detection by multiple independent anti‑phishing services suggests that the infrastructure was deliberately provisioned to mimic BlockDAG support channels.
At present, no additional artifacts such as phishing landing page content or credential‑harvesting scripts have been publicly disclosed, leaving the exact attack vector uncertain. Defenders should continue to block the domain at perimeter filters, monitor for any re‑hosting attempts, and advise users that any unsolicited communications referencing BlockDAG that originate from blockdaghelp.network are untrusted.
Last checked
For this gTLD, 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.
ns2.prohoster.ccblockdaghelp.networkpriority 0Location describes the IP network.
26c889b812ce4885cf9bf3d15523fd595bd3e7e8344d8ba8222cc5aca47c62e7Saved 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.
blockdaghelp.network
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
audit_replace→https://radar.cloudflare.com/scan/82de08d6-392d-4b5c-b019-9b82c29555c9
1→2
https://radar.cloudflare.com/scan/93249def-def4-4b8d-993b-aae6e3af2b6f
0→1
3/91 engine detections
View sourceNo threat flag
View sourceblockdaghelp.network
View sourcePD-20260305-1EB3B2
1 topluluk üyesi tarafından bildirildi; ilk görülme 05.03.2026
PD-20260305-1EB3B2 Recipient: abuse.webltd@gmail.com Hesap kimlik bilgilerini, kişisel bilgileri veya ödeme bilgilerini girdiyseniz ya da bu alan adından bir dosya indirdiyseniz hemen harekete geçin. Aşağıda olayı bildirmenize ve kendinizi korumanıza yardımcı olacak kaynaklar bulunmaktadır.
resmi siber suç iletişim bilgileri veya şikayet taslağı oluştur → almak için ülkenizi seçin.
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 ↗
blockdaghelp.network)Tüm ayrıntıları bilmeseniz bile — yine de şikayette bulun. Kısmi bilgiler de soruşturmalara yardımcı olmaktadır.
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
Saklanan engelleme listesi, WHOIS, DNS ve genel tarama kanıtlarını kullanarak tehdit analizi
Şimdi TaraŞüpheli alan adlarını tehdit veritabanımıza bildirin — topluluğu koruyun
BildirSon kimlik avı raporları ve gözlemlenen kullanılabilirlik değişiklikleri
İzleCanlı tehditleri izleyin veya bunun yanlış bir uyarı olduğunu düşünüyorsanız bu kayda itiraz edin
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.