Security engines reporting a detection: 17. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
This domain, proposal-zebec.network, operates as a crypto brand impersonation phishing site targeting users of the legitimate Zebec Network platform. Analysis indicates the domain mimics Zebec Network’s real-time crypto payroll and payment services, likely to harvest credentials, private keys, or facilitate unauthorized token transfers. The page title, 'Zebec Network | Real-Time Crypto Payroll & Payments,' directly replicates the legitimate service’s branding, increasing the likelihood of user deception. Given the domain’s focus on crypto-related functionality, the primary threat is likely credential theft or crypto drainer attacks, where victims unknowingly authorize malicious transactions. Infrastructure analysis reveals multiple high-risk indicators. The domain was registered on April 28, 2026, through PDR Ltd. d/b/a PublicDomainRegistry.com, a registrar frequently associated with phishing and fraudulent domains. VirusTotal reports 17 out of 95 security vendors flagging the domain as malicious, while it appears on three independent security blocklists. The domain previously resolved to IP address 188.114.97.3, a host with a history of supporting phishing infrastructure. Additionally, the domain was detected in one AlienVault OTX threat intelligence pulse, further corroborating its malicious intent. Users who interacted with proposal-zebec.network should assume potential compromise of sensitive data, including wallet credentials or private keys. Immediate actions include revoking any active smart contract approvals or token allowances granted to unknown addresses, rotating passwords for associated accounts, and monitoring transaction histories for unauthorized activity. If crypto assets were transferred, victims should report the incident to relevant blockchain explorers and law enforcement. All interactions with the domain should be treated as high-risk, and users are advised to verify the authenticity of any crypto-related service through official channels before engaging.
Extracted from stored page analysis
Observed indicators
0 wallet · 1 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
Telegram
https://t.me/zebecprotocolStored page reference
IoC extraction recorded 2026-08-01 04:13:42 UTC
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='proposal-zebec.network', port=80): Max retries exceeded with url: / (Caused by NewConnecti
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
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 DetectedApr 28, 2026
IoC Extractionscanned Aug 1, 20260 wallet · 1 Telegram IoC
Submitted URLhttp://proposal-zebec.network/
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
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.
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:09:41 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-06-16 22:11:43 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-16 22:11:43 UTC → 2026-09-30 16:14:55 UTC · 2,538.05hmidpoint estimate ≈ 2026-08-08 19:13:19 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.
VirusTotal Detections Update2026-06-26 04:48:19 UTC
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
proposal-zebec.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 12, 2026
Time to First Unavailability
2409 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 linked1 reports recordedContent unavailable
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 · proposal-zebec.network
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.
