VirusTotal
4 / 89 engine detections
보고서 열기“Ripe Deposit — Deposit GREEN & Swap RIPE Token”
ripe.run — 콘텐츠를 사용할 수 없음. 사기 유형: Crypto Drainer. 증거 요약: VirusTotal 4/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, VIPRE); URLQuery 1 alert; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 80/100. 등록기관: PDR.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
4 / 89 engine detections
보고서 열기1 threat-system alert
보고서 열기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.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | ripe.run |
malicious | Sinkholed |
PhishDestroy threat report
ripe.run presented itself as a token deposit and swap service under the branding "Ripe Deposit," soliciting users to deposit GREEN tokens and swap RIPE tokens. It targets cryptocurrency holders who interact with DeFi platforms and token swap interfaces. PhishDestroy first identified it on 2026-09-19, one day after the domain was registered. The site is now dead and has been DNS-inactive since 2026-09-20.
Wallet drainers work by prompting visitors to connect their crypto wallets to a fraudulent interface that mimics a legitimate DeFi or token platform. Once a wallet is connected, the site requests transaction approvals or signatures that secretly authorize the drainer contract to transfer the victim's tokens and assets to attacker-controlled addresses. In this case, the page title references depositing and swapping tokens, which is a common lure to make the approval request feel routine. The victim loses all assets covered by the granted approvals, often within seconds.
VirusTotal flagged ripe.run on 2026-09-19 with 4 detections out of 89 engines, identified by alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, and VIPRE. While 4 detections is a relatively low count, the site was also added to three independent blocklists: PhishDestroy, MetaMask, and SEAL. MetaMask's inclusion is particularly significant, as it means users of that wallet would have received an active warning before interacting with the site.
The domain was registered on 2026-09-18 through PDR Ltd. d/b/a PublicDomainRegistry.com, giving the operators just one day between registration and PhishDestroy's detection. It was hosted on Cloudflare's network with a Canadian-geolocated IP and secured with a Let's Encrypt TLS certificate issued under the YE1 authority. The combination of a same-day registration and free TLS certificate is consistent with disposable infrastructure built for short-lived fraud campaigns.
If you visited ripe.run and connected your wallet, immediately revoke all token approvals granted during that session using a trusted approval management tool, then transfer remaining assets to a fresh wallet address. Do not interact with any tokens or contracts that appeared on the site. If you signed any transaction, assume your approvals are compromised and act without delay. Security teams and wallet providers should ensure ripe.run and any associated contracts are present on their blocklists; the domain is already inactive but the drainer contract may still be live on-chain.
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 평판은 이 도메인에 귀속되지 않습니다.
anton.ns.cloudflare.comkara.ns.cloudflare.comLocation describes the IP network.
f7a1612cb19c36dabde2683689b41119f0af4e829d4167a70e2cd1823f2ccbd5Saved 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 ripe.run · 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.
ripe.run
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
접속 가능→이용 불가
접속 가능
No threat flag
View sourcePD-20260919-6B5CD3
Page captured
View source4/89 engine detections
View sourceripe.run
View sourcePD-20260919-6B5CD3 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 ↗
ripe.run)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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.