VirusTotal
7 / 91 engine detections
보고서 열기“Zengo Wallet – Secure Keyless Crypto Wallet”
피싱: zengo.created.app — 마지막으로 알려진 활성 (HTTP 200). 증거 요약: VirusTotal 7/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Kaspersky, SOCRadar); 2 external…
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
7 / 91 engine detections
보고서 열기no community references
보고서 열기provider verdict: clean
보고서 열기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
zengo.created.app is a phishing page impersonating Zengo, the keyless crypto wallet. It presents itself under the title "Zengo Wallet – Secure Keyless Crypto Wallet" to convince Zengo users and people searching for the app that they have reached the genuine product. PhishDestroy first detected it on 2026-09-19. As of 2026-10-19 the site was still online and serving its content.
Impersonation pages like this copy a trusted wallet's branding so victims let their guard down, then steer them into handing over whatever controls their funds. Zengo's real selling point is that it has no seed phrase, so a fake that promises "keyless" security can catch users off guard with a login, "recovery", "verification" or wallet-connection step the real app would never ask for through a third-party web page. Anything entered or approved there goes to the operators, who can then empty the linked wallet. Stolen crypto is effectively unrecoverable.
Seven of 91 VirusTotal engines flagged the domain when it was checked on 2026-09-29: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Kaspersky, SOCRadar, VIPRE and Webroot. That count is modest, so many browsers and filters may still let it through. Wallet-focused defenses are more decisive here. Besides PhishDestroy, the domain sits on the MetaMask and SEAL blocklists, which matters because those lists protect users at the moment they interact with a wallet.
The page lives on a subdomain of created.app. The 2023-07-12 registration date through Name.com, Inc. belongs to that parent domain, so it does not show when this particular lure was set up. Hosting is on Amazon.com, Inc. infrastructure in the US, and the Let's Encrypt certificate gives the page a padlock. That padlock says nothing about whether the site is legitimate.
If you visited this page, do not return to it, and reach Zengo only through the official app from your device's app store. If you entered login, recovery or verification details, or connected a wallet, move any remaining funds to a new wallet you control and contact Zengo support through the app. If you connected another wallet, revoke any token approvals granted during that session. Security teams should block the hostname, look for traffic to it in their logs, and report it to the hosting provider and to other blocklists that do not yet flag it.
Last checked
For the registrable domain created.app 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.
Edge-IP 평판은 이 도메인에 귀속되지 않습니다.
ns2.vercel-dns.comLocation describes the IP network.
939dcd2ea88a9fb0cdc440fbfa55064376759753b259b34a3242d277c46010ebSaved 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 zengo.created.app · checked Sep 19, 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.
zengo.created.app
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
protected→live_content
content_served
알 수 없음→protected
http_access_restricted · access_restriction
알 수 없음→live_content
content_served
live_content→protected
http_access_restricted · access_restriction
알 수 없음→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
5→6
4→5
3→4
1→3
No threat flag
View source7/91 engine detections
View sourcezengo.created.app
View sourceListed 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 ↗
zengo.created.app)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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.