On 2026-10-04, aevachain.org was listed on both the MetaMask and SEAL blocklists, according to separate source records. The domain also appeared in an internal listing by PhishDestroy on the same date, reflecting attention from multiple monitoring sources.
Recorded Evidence
MetaMask included aevachain.org on its blocklist as of 2026-10-04. SEAL also listed the domain on its blocklist on that date. An internal listing was recorded by PhishDestroy for the domain on 2026-10-04. The domain was registered through NAMECHEAP INC on 2026-09-27, and its SSL certificate from Let's Encrypt / YE2 was scanned on 2026-10-04.
Interpretation
The records from MetaMask, SEAL, and PhishDestroy indicate that aevachain.org was observed by several monitoring sources on the same date. These observations are limited to the specific dates and sources named, providing a snapshot of the domain's status at that time without further context about its activity or content.
Recommended Actions
For aevachain.org, retain the blocklist records from MetaMask and SEAL, as well as the PhishDestroy internal listing, for ongoing reference. Compare these historical records with any future monitoring results to track changes or new observations related to the domain.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-04 06:06:24 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-04 06:06:24 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Threat First Observed2026-10-04 06:05:00 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 31.43.161.6.
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
8 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
aevachain.org detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Blocklist Detection
Found in 2 blocklists: MetaMask, SEAL
Oct 4, 2026
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Oct 4, 2026
Sent Report Recorded
Stored outgoing record associated with registrar NAMECHEAP INC, 2 abuse contacts
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · aevachain.org
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches1
Same favicon hash or the same page title as this host.
(IS)
