VirusTotal
3 / 91 engine detections
Bericht öffnen“Medusa Drainer”
Krypto-Wallet-Drainer: medusa.services — Letzter bekanntermaßen aktiv (HTTP 302). Zusammenfassung der Beweislage: VirusTotal 3/91 (alphaMountain.ai, Chong Lua…
Die ausführliche Analyse von PhishDestroy AI bleibt auf Englisch, damit der ursprüngliche forensische Bericht unverändert bleibt.
3 / 91 engine detections
Bericht öffnen23 community references
Bericht öffnenprovider verdict: clean
Bericht öffnenNo threat flag
Bericht öffnenNo malicious flag
Bericht öffnenResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
The domain medusa.services is an active cryptocurrency phishing site engaged in brand impersonation targeting Aave, a decentralized finance protocol. It operates as a crypto drainer, designed to trick users into connecting wallets and signing malicious transactions that siphon funds. No legitimate association with Aave or any known drainer kit exists; the site remains live and poses an elevated risk to visitors.
Technical indicators confirm medusa.services as a threat. Two of 95 VirusTotal security vendors, including Gridinsoft and Seclookup, flag the domain, while Gridinsoft assigns a trust score of 0/100. It appears on one security blocklist (PhishDestroy) but is not flagged by Google Safe Browsing. The domain is registered through Cloudflare, Inc., resolves to IP 104.21.60.48 (US, AS13335 Cloudflare, Inc.), and uses nameservers kimora.ns.cloudflare.com and memphis.ns.cloudflare.com. The SSL certificate is issued by GoDaddy.com, Inc. via Go Daddy Secure Certificate Authority - G2. Detected technologies include Nginx and OpenResty, and the observed page title is 'Medusa Drainer', returning an HTTP 403 status.
Users who interacted with medusa.services should immediately revoke all token approvals via a blockchain explorer or wallet interface and transfer remaining funds to a new, secure wallet. Monitor transaction history for unauthorized activity and report the domain to platforms like PhishTank, Google Safe Browsing, or the impersonated brand (Aave) for takedown. Enable two-factor authentication on all accounts and avoid reusing passwords to mitigate further risk.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/mazovdusaStored page referenceIoC extraction recorded 2026-07-29 02:44:28 UTC
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.
Die Edge-IP-Reputation wird dieser Domäne nicht zugeordnet.
kimora.ns.cloudflare.commemphis.ns.cloudflare.comLocation describes the IP network.
885543f43b1326b096c6ae18f92fc4eabe396cb099a8df73138a0b728f1c456fSaved 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 medusa.services · checked Mar 2, 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.
redirect: raw=redirect_302; http=302; via=https_proxy; location=https://domains.atom.com/lpd/name/medusa.services; server=openresty
medusa.services
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
2→4
No threat flag
View source23 community references
View source3/91 engine detections
View sourcePage captured
View sourcemedusa.services
View source95 gespeicherte ähnliche Domains
Von 1 Community-Mitglied gemeldet; erstmals gesehen am 25.09.2025
Listed domains receive at least one abuse report; this entry has no retained notification history.
Wenn Sie mit dieser Domain interagiert, persönliche Daten eingegeben oder eine Kryptowährungs-Wallet verbunden haben, ergreifen Sie sofort Maßnahmen. Nachfolgend finden Sie Ressourcen, die Ihnen helfen, den Vorfall zu melden und sich zu schützen.
Wählen Sie Ihr Land aus, um Offizielle Kontakte im Bereich Cyberkriminalität oder einen Beschwerdeentwurf erstellen → zu erhalten.
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.
Schätzungsweise $51 billion flossen im Jahr 2024 in illegale Krypto-Wallets (source). Falls Sie mit medusa.services — Handeln Sie jetzt.
Wallet-specific steps below apply if you connected a wallet, signed a transaction, or exposed a wallet secret.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Laut der FBI, wobei die wichtigsten Angaben die Transaktionsdaten sind:
0x5856...35985)medusa.services)Auch wenn dir nicht alle Details bekannt sind — trotzdem Anzeige erstatten. Auch unvollständige Informationen sind für die Ermittlungen hilfreich.
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
Bedrohungsanalyse anhand gespeicherter Blocklisten, WHOIS, DNS und öffentlicher Scan-Beweise
Jetzt scannenMelden Sie verdächtige Domains an unsere Bedrohungsdatenbank – schützen Sie die Community
MeldenAktuelle Phishing-Meldungen und beobachtete Verfügbarkeitsänderungen
ÜberwachenBeobachten Sie aktuelle Bedrohungen oder legen Sie Widerspruch gegen diesen Eintrag ein, wenn Sie der Meinung sind, dass es sich um einen Fehlalarm handelt
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.