VirusTotal
2 / 89 engine detections
レポートを開く“Home | Dapps Leading Synthetic Protocol”
blocdeck.com exposed as Fake Investment Platform Phishing Site. Resolves to 194.164.64.55. Check the full report.
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
2 / 89 engine detections
レポートを開く1 threat-system alert
レポートを開くchecked — no match recorded
no community references
レポートを開くprovider verdict: clean
レポートを開く14 確認済み — ブロックなし
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 |
|---|---|---|---|
| YARAhub by abuse.ch | www.blocdeck.com/assets/main.bmwhmhgr.js |
malware | Detects file containing Telegram Bot API |
PhishDestroy threat report
PhishDestroy identifies blocdeck.com as an active Fake Investment Platform Phishing site under current investigation. The domain is engineered to deceive users into believing it is a legitimate investment platform, specifically mimicking trusted financial service interfaces. This tactic is commonly used to harvest sensitive financial data or initiate unauthorized fund transfers. Users entering credentials or payment details risk direct financial compromise and identity theft. Immediate user caution is advised.
This domain was flagged with zero detections across 95 VirusTotal engines as of the latest scan, indicating it has not yet been widely recognized by automated scanners. blocdeck.com was registered through HOSTINGER operations, UAB on April 1, 2026, and resolves to IP address 194.164.64.55 using a Let's Encrypt SSL certificate. The domain’s recent creation date, combined with its low detection rate, suggests a recently launched attack with high potential for evading early detection systems. No entries were found on major blocklists at the time of assessment, and trust scores from domain reputation services remain unverified due to its nascency.
To mitigate exposure, users should avoid accessing blocdeck.com entirely and report the domain to their financial institutions and cybersecurity platforms. Organizations are advised to block the domain at DNS and firewall levels and inspect internal traffic for connections to 194.164.64.55. If credentials were entered, users must immediately change passwords, revoke payment methods, and monitor accounts for fraudulent activity. Security teams should treat this as a high-priority threat and update threat intelligence feeds accordingly.
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.
artemis.dns-parking.comhermes.dns-parking.comLocation describes the IP network.
d8483315f04ffabdc719eb44d8ea13fbc1a4ea918ba785651910502cf2c43ae3blocdeck.comSaved 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 duplicate-disabled-213935.invalid · checked May 5, 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.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-213935.invalid', port=80): Max retries exceeded with url: / (Caused by
duplicate-disabled-213935.invalid
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
到達可能→利用不可
2/89 engine detections
View sourceNo threat flag
View sourceduplicate-disabled-213935.invalid
View sourceListed 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 ↗
duplicate-disabled-213935.invalid)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.