VirusTotal
3 / 89 engine detections
보고서 열기“Canton Network Wallet Application”
The domain wallet.validator.test.canton.obsidian.systems was registered on May 16 2026 through NameCheap, Inc.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
3 / 89 engine detections
보고서 열기no community references
보고서 열기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
The domain wallet.validator.test.canton.obsidian.systems was registered on May 16 2026 through NameCheap, Inc. It resolves to the public IPv4 address 52.1.44.192, which belongs to an Amazon Web Services EC2 instance in the us‑east‑1 region. The hosting infrastructure is typical for short‑lived malicious deployments, leveraging AWS’s global DNS and compute resources to obtain a readily reachable endpoint. Infrastructure analysis shows the domain is delegated to four Amazon Route 53 name servers: ns-1861.awsdns-40.co.uk, ns-391.awsdns-48.com, ns-1084.awsdns-07.org, and a fourth entry truncated in the source data. The web server returns HTTP 200 for default requests and presents an Amazon‑issued RSA 2048‑M01 certificate, confirming the use of AWS Certificate Manager. Gridinsoft’s trust scoring assigns a rating of 0 / 100, indicating a reputation of extreme distrust. Threat intelligence classifies the site as a crypto‑drainer, a pattern that typically lures cryptocurrency wallet users into submitting private keys or signing malicious transactions. The domain appears on a single security blocklist and is currently blocked by PhishDestroy. VirusTotal analysis records a single positive detection out of 95 scanners, reinforcing the low‑visibility but high‑risk nature of the operation. The combination of a fresh registration, zero trust score, and a valid SSL certificate is consistent with a fast‑flux style fraud campaign. Defenders should add wallet.validator.test.canton.obsidian.systems to DNS blocklists and enforce outbound filtering for connections to the 52.1.44.192 address. Network telemetry should be inspected for anomalous HTTP 200 responses from the AWS region, and any credential submission to the domain must be treated as compromise. Continuous monitoring of the associated name servers is advised, as the attacker may shift the underlying IP address while retaining the same domain registration.
For the registrable domain obsidian.systems 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.
ns-721.awsdns-26.netLocation describes the IP network.
f91aeaa9a5168f32233752ece778335fdbb0f8be5256b72d394c4d98b2d78d29Saved 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.
alive_content: raw=ok; http=200; via=https_proxy; server=nginx/1.31.5
wallet.validator.test.canton.obsidian.systems
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
No threat flag
View source3/89 engine detections
View sourcewallet.validator.test.canton.obsidian.systems
View source저장된 유사 도메인 187개
전체 187개 중 100개 표시
커뮤니티 구성원 1명이 신고 · 최초 확인 2026년 5월 16일
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 ↗
wallet.validator.test.canton.obsidian.systems)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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.