Security engines reporting a detection: 19. Public blocklists reporting a match: 3. Exercise extreme caution — do not enter credentials or personal information.
This website does not have many visitors We could not analyze the content of the site Maltiverse has identified this website as being potentially harmful IPQS flagged this website for Phishing IPQS has flagged this website as suspicious
Network Security Intelligence Registrar context
Registrar contextNameSilo
Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
This domain, corev3-secure-b4df72d1-ff44b36-ae57.network, is a high-risk crypto drainer impersonating the legitimate WalletConnect service. It poses a significant threat to users by attempting to steal their cryptocurrency wallet credentials and private keys, which can lead to unauthorized access and financial loss.
Analysis indicates that the domain has been flagged by 19 out of 95 security vendors on VirusTotal, suggesting a notable level of malicious activity. The domain was registered through NameSilo, LLC on November 28, 2025, and currently resolves to an IP address located in the United States (98.84.224.111) under the Autonomous System AS14618, which is owned by Amazon.com, Inc. Additionally, the domain appears on four security blocklists, including PhishDestroy, Polkadot, Enkrypt, and Codeesura, further confirming its malicious nature. Notably, the domain does not have an SSL certificate, which is a common indicator of phishing sites.
If users have visited corev3-secure-b4df72d1-ff44b36-ae57.network, they should immediately check their cryptocurrency wallets for any unauthorized transactions and consider changing their wallet passwords and private keys. It is also recommended to enable two-factor authentication (2FA) and to monitor their accounts for any suspicious activity. Users should report the incident to their wallet provider and any relevant security organizations to help mitigate the risk.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not observedNo cloaking was observed in the stored scan
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='corev3-secure-b4df72d1-ff44b36-ae57.network', port=80): Max retries exceeded with url: / (
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
RegistrationCreated Nov 28, 2025 (317d)—Expires Nov 28, 2026
Time to First Unavailability163 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedNov 29, 2025
DOM Analysisanalyzed Apr 23, 2026score 100/1001 brand signal
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.
Accreditation is a contract, not a safety certification.
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.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
98.84.224.111
Network ASN
AS14618
Organization
Amazon.com, Inc.
Observed location
Ashburn, US
Server header
Netlify
Edge-IP reputation is not attributed to this domain.
Nameservers 4
dns1.p06.nsone.net
dns2.p06.nsone.net
dns3.p06.nsone.net
dns4.p06.nsone.net
Location describes the IP network.
TLS certificate
Valid from
2025-11-28 10:14:52
Valid until
2026-02-25 10:14:52
Hostname coverage
Hostname coverage not recorded
Validity
Stored certificate expired
Collection time
2026-06-17 22:00:48 UTC
Collection source
PhishDestroy collector
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:08:22 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-06-17 22:13:25 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-17 22:13:25 UTC → 2026-09-30 16:14:55 UTC · 2,514.03hmidpoint estimate ≈ 2026-08-09 07:14:10 UTC · precision very low · basis bounded
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.
14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
corev3-secure-b4df72d1-ff44b36-ae57.network 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.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
May 11, 2026
Time to First Unavailability
3923 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
6 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If a wallet, seed phrase, or account was exposed, report the incident immediately. Revoke approvals and move remaining assets to a new wallet created on a trusted device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Guaranteed crypto recovery is a fraud indicator. Learn more about recovery fraud →
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 matches4
Same favicon hash or the same page title as this host.
An estimated $51 billion flowed to illicit crypto wallets in 2024 (source). If you interacted with corev3-secure-b4df72d1-ff44b36-ae57.network — act now.
What should I do immediately?
Urgent
Revoke token approvals — use revoke.cash to remove access granted to malicious smart contracts
Move remaining funds to a brand-new wallet. The compromised wallet is no longer safe
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
According to the FBI, the most important details are transaction data:
Chainabuse — flag scam wallets across exchanges & platforms
Your crypto exchange — notify its fraud team immediately; it may be able to preserve records or restrict funds held on its platform
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do crypto scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Malicious approvals — "connect wallet" prompts that grant unlimited token spending to attackers
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
Fake ads & airdrops — Google/social media ads and "free token" offers leading to wallet drainers
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Use a hardware wallet (Ledger, Trezor). Never store large amounts in browser wallets
Bookmark official sites — never click links from emails, DMs, or ads
Read every approval — verify permissions before signing. Reject unlimited approvals
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
HTML · IFRAME
Embed This Report
Share this threat intelligence on your website or blog
READ-ONLY
embed.html
<iframesrc="https://phishdestroy.io/embed/domain/corev3-secure-b4df72d1-ff44b36-ae57.network"title="PhishDestroy threat report for corev3-secure-b4df72d1-ff44b36-ae57.network"width="100%"height="320"loading="lazy"referrerpolicy="no-referrer"sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"style="border:0;border-radius:12px;max-width:100%"></iframe>
(US)
PhishDestroy Investigation
