VirusTotal
1 / 91 engine detections
보고서 열기“Zebec Network | Real‑Time Crypto Payroll & Payments”
app-zebec.network — 콘텐츠를 사용할 수 없음. 사기 유형: Credential Phishing. 증거 요약: VirusTotal 1/91 (ChainPatrol); URLQuery 1 alert; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 71/100. 등록기관: PDR.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
1 / 91 engine detections
보고서 열기1 threat-system alert
보고서 열기Suspicious
보고서 열기1/12
1/100
보고서 열기checked — no match recorded
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.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Quad9 DNS | app-zebec.network |
malicious | Sinkholed |
PhishDestroy threat report
On May 15, 2024, PhishDestroy identified the domain app-zebec.network as a credential harvesting endpoint engaged in active phishing campaigns. The domain mimics legitimate financial services to deceive victims into surrendering login credentials, posing a significant risk to enterprise and personal users alike. Current telemetry confirms ongoing malicious activity, warranting immediate defensive measures. This domain, registered through PDR Ltd. d/b/a PublicDomainRegistry.com, was created on April 29, 2026, and resolves to the IP address 188.114.97.3. VirusTotal analysis reveals that 1 of 95 security vendors flagged this domain for malicious activity, with no observed blocklist presence at this time. The SSL certificate, issued by Let’s Encrypt, may lend an air of legitimacy, though issuance mechanisms are frequently abused by threat actors to evade detection. Further, the domain’s recent creation date suggests opportunistic registration targeting current events or trending financial narratives. As of this advisory, app-zebec.network remains active and is actively resolving to its associated IP. Organizations and users are strongly advised to block this domain at the network perimeter and DNS level to prevent user exposure. Implementing browser-based controls such as safe browsing policies and endpoint detection rules (e.g., YARA signatures) is recommended to mitigate risk. Additionally, users should be reminded to verify website authenticity via multi-factor authentication and to avoid clicking on unsolicited links purporting to originate from financial institutions. Continuous monitoring of this domain and associated infrastructure is advised due to the evolving nature of credential harvesting campaigns.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/zebecprotocolStored page referenceIoC extraction recorded 2026-08-01 04:13:25 UTC
Last checked
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.
Edge-IP 평판은 이 도메인에 귀속되지 않습니다.
anahi.ns.cloudflare.comgerald.ns.cloudflare.comLocation describes the IP network.
bf9ecb329ed598d5f781feb85029cb583508339c1bf734dde4748b391fd38d6aSaved 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 app-zebec.network · checked Apr 29, 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='app-zebec.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
app-zebec.network
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
알 수 없음→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
1/91 engine detections
View sourceNo threat flag
View sourceapp-zebec.network
View sourcePD-20260429-F0243C
커뮤니티 구성원 1명이 신고 · 최초 확인 2026년 4월 29일
PD-20260429-F0243C Recipient: abuse@publicdomainregistry.com Registrar: PublicDomainRegistry (PDR Ltd.) (India) Policy Violations: Explicit policy to immediately suspend domains used for phishing, 419 scams, identity fraud, malware distribution without prior notice Applicable Laws: IT Act 2000 §§66C–66D (identity theft, cheating by personation), Indian Penal Code §420 / Bharatiya Nyaya Sanhita §318 (fraud)
계정 자격 증명, 개인 정보 또는 결제 정보를 입력했거나 이 도메인에서 파일을 다운로드한 경우 즉시 조치를 취하세요. 다음은 사건을 신고하고 자신을 보호하는 데 도움이 되는 리소스입니다.
공식 사이버 범죄 연락처 또는 불만사항 초안 작성 →를 받으려면 국가를 선택하세요.
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 ↗
app-zebec.network)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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.