Zum Sicherheitsbericht springen
Analytics-Dashboard
Domänensicherheit und Bedrohungsinformationen
hyperliquid-btc.com favicon

hyperliquid-btc.com

“Hyperliquid | Exchange Platform”

Registrar
Hosting Concepts
Resolved IP
130.12.180.154
PhishDestroy assessment Kritisch
Verfügbarkeit Letzter bekanntermaßen aktiv Letzte gespeicherte Erreichbarkeitsbeobachtung Beobachtet · HTTP probe
Risikosignale
VirusTotal-Erkennungen: 4/92 Spamhaus DBL: DBL_SPAM Gespeicherte Sperrlistenübereinstimmungen: 2 Automatische Markenkennung: Hyperliquid
OTX: 4 refs 21.10.2026 1 Report Sent
API
Diese Domain wurde als bösartig markiert.
Sicherheits-Engines melden eine Entdeckung: 4. Öffentliche Blocklisten, die eine Übereinstimmung melden: 2. Seien Sie äußerst vorsichtig – Geben Sie keine Anmeldeinformationen oder persönlichen Daten ein.
VirusTotal
4 / 92
engine detections
Google Safe Browsing
No threat flag
OTX
4
community references
Page captures
5
open gallery
Reports sent
1
view timeline
Berichtsübersicht

Hyperliquid-Imitation: hyperliquid-btc.com — Letzter bekanntermaßen aktiv (HTTP 200). Zusammenfassung der Beweislage: VirusTotal 4/92 (alphaMountain.ai…

Die ausführliche Analyse von PhishDestroy AI bleibt auf Englisch, damit der ursprüngliche forensische Bericht unverändert bleibt.

Source evidenceVirusTotal 4 / 92 · OTX 4 references 7 sources

Spamhaus DBL

DBL_SPAM

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Kritisch
VirusTotal
4 / 92
OTX
4 community refs
Page captures
5
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy’s automated assessment classified hyperliquid-btc.com as an impersonation phishing page targeting the Hyperliquid brand. The recorded page title reads “Hyperliquid | Exchange Platform” and the domain was first seen by PhishDestroy on 2026-10-21, two days after its registration on 2026-10-19, with an HTTP 200 response recorded on that date.

How the scam works

Impersonation phishing sites copy the visual design, branding and naming of a legitimate service to lure users into entering login credentials, private keys, or approving wallet transactions. Victims who trust the familiar brand may inadvertently disclose sensitive information that can be harvested for unauthorized account access or fund transfers.

Evidence

VirusTotal scanned the domain on 2026-10-21 and reported four detections across 92 engines, including one malicious label and three suspicious labels from alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet and SOCRadar. Google Safe Browsing checked the domain on the same day and did not flag it. External blocklists MetaMask and SEAL listed the domain, Spamhaus DBL marked it as spam, and OTX recorded four pulses referencing it, all on 2026-10-21. URLScan captured the site on 2026-10-21; its engine verdict marked it malicious with a score of 99, while the overall score was reported as 0.

Infrastructure

The domain was registered with Hosting Concepts B.V. d/b/a Registrar.eu on 2026-10-19 and set to expire on 2027-10-19. It resolved to the recorded IP 130.12.180.154, which was listed under the network Omegatech LTD in the Netherlands. A Let’s Encrypt TLS certificate for hyperliquid-btc.com was issued on 2026-10-20 and was valid until 2027-01-18. The server identified itself as openresty running on an Nginx/OpenResty stack, with ports 22, 80, 443 and 3000 observed open at the time of capture.

What to do

Users should avoid entering any Hyperliquid credentials or approving wallet connections on this domain; if credentials were entered, they should be changed immediately. Organizations should block hyperliquid-btc.com in web filters, monitor outbound traffic for connections to the domain, and review logs for any access attempts. Security teams should add the domain to threat‑intel feeds and apply appropriate incident‑response procedures if any credential or wallet data was submitted.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportURLQuery reportStored capture screenshotCloudflare Radar screenshot (2026-10-21T09:05:35Z)URLQuery screenshotURLScan screenshot (2026-10-21T08:38:03Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

URLScan · 2026-10-21T08:32:16Z

Beobachtet: · Retrieved:

Uuid
01a15d96-d347-70c8-b711-2142d1c12098
Final url
https://hyperliquid-btc.com/
Status
200
Weitergeleitet
https-only
Redirects
[
    {
        "to": "https://hyperliquid-btc.com/",
        "from": "http://hyperliquid-btc.com/",
        "status": 307
    }
]
Ip
130.12.180.154
Contacted domains
[
    "fonts.gstatic.com",
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "142.250.217.131",
    "192.179.18.95",
    "130.12.180.154"
]
Asns
[
    "15169",
    "202412"
]
Countries
[
    "US",
    "NL"
]
Document hash
178d1840af1d0c86dd622c1c5fa114d1bfea42601a9c25a26058d2153d145ca1
Globals
[
    "render",
    "prog",
    "countUp",
    "io",
    "asks",
    "bids",
    "mid",
    "price",
    "links",
    "secIO"
]
Tls
{
    "san": [
        "hyperliquid-btc.com",
        "www.hyperliquid-btc.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "hyperliquid-btc.com",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-18T17:34:43Z",
    "valid_from": "2026-10-20T17:34:44Z"
}
Domain age days
0
Apex age days
0
Tls age days
0
Tls valid days
89
Requests
7
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "openresty",
    "content-type": "text/html"
}
Cloudflare Radar · 2026-10-21T09:05:35Z

Beobachtet: · Retrieved:

Uuid
06841088-46b5-4ac6-8b2a-cecea6f00ea3
Final url
https://hyperliquid-btc.com/
Status
200
History
[
    {
        "url": "https://hyperliquid-btc.com/",
        "status": 200
    }
]
DOM structure hash
26364f4224966e0662a0e66114974df530b6e1538c88f6da4760d72cba526cc4
Document hash
178d1840af1d0c86dd622c1c5fa114d1bfea42601a9c25a26058d2153d145ca1
Domain risks
[
    "New Domains",
    "Security Risks",
    "Newly Seen Domains"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "hyperliquid-btc.com",
        "type": "A",
        "value": "130.12.180.154"
    }
]
Dnssec valid
false
Ip
130.12.180.154
Registration record
{
    "registrar": "Hosting Concepts B.V. d/b/a Registrar.eu",
    "created": "2026-10-19T17:22:40Z",
    "updated": "2026-10-19T17:22:43Z",
    "expires": "2027-10-19T17:22:40Z",
    "nameservers": [
        "a.dnspod.com",
        "b.dnspod.com",
        "c.dnspod.com"
    ]
}
VirusTotal · 2026-10-21T09:08:01Z

Beobachtet: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 1,
    "suspicious": 3,
    "undetected": 35
}
Vendor labels
{
    "Fortinet": "spam",
    "SOCRadar": "suspicious",
    "alphaMountain.ai": "spam",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "alphaMountain.ai": "Spam (alphaMountain.ai)"
}
Registrar
Hosting Concepts B.V. d/b/a Registrar.eu
Erstellt
2026-10-19T17:22:40Z
Expires
2027-10-19T17:22:40Z
Updated
2026-10-19T19:22:43Z
First seen
2026-10-20T18:45:30Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "c.dnspod.com"
    },
    {
        "ttl": 180,
        "type": "SOA",
        "rname": "domainadmin.dnspod.com",
        "value": "a.dnspod.com"
    },
    {
        "ttl": 600,
        "type": "A",
        "value": "130.12.180.154"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "a.dnspod.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "b.dnspod.com"
    }
]
Dns at
2026-10-21T09:13:21Z
Jarm
27d40d40d00040d00042d43d000000e1ea2a807a629b496b664cf07ad7c08d
Certificate
{
    "san": [
        "hyperliquid-btc.com",
        "www.hyperliquid-btc.com"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "53b918baa4760b07f37aa5d8a05162825b5",
    "sha256": "ffed0b2c76f31f655ff9a3c970b0cba8f61c29ebee2245fd7b4e08be855fb590",
    "subject": "hyperliquid-btc.com",
    "valid_to": "2027-01-18T17:34:43Z",
    "valid_from": "2026-10-20T17:34:44Z"
}
Registration record
{
    "registrar": "Hosting Concepts B.V. d/b/a Registrar.eu",
    "registrar_iana_id": "1647",
    "registrar_url": "http://www.openprovider.com",
    "created": "2026-10-19T17:22:40Z",
    "updated": "2026-10-19T17:22:43Z",
    "expires": "2027-10-19T17:22:40Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "a.dnspod.com",
        "b.dnspod.com",
        "c.dnspod.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "expiration": "2027-10-19T17:22:40Z",
        "registration": "2026-10-19T17:22:40Z",
        "registrar expiration": "2027-10-19T17:22:40Z",
        "last update of RDAP database": "2026-10-20T18:45:20Z"
    }
}
Website checks · 2026-10-21T09:07:04Z
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "hyperliquid-btc.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-21T08:34:18Z",
    "first": "2026-10-21T08:34:18Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 13016
}
Crawler rules
{
    "agents": [
        "Amazonbot",
        "Applebot-Extended",
        "Bytespider",
        "CCBot",
        "ClaudeBot"
    ],
    "present": true,
    "sitemaps": [
        "https://hyperliquid-btc.com/sitemap.xml"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 1
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        80,
        443,
        3000
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "220.196.136.75",
            "host": "b.dnspod.com"
        },
        {
            "ip": "43.134.249.75",
            "host": "c.dnspod.com"
        },
        {
            "ip": "117.135.128.175",
            "host": "a.dnspod.com"
        }
    ],
    "zone": "hyperliquid-btc.com"
}
Location
{
    "ip": "130.12.180.154",
    "asn": "202412",
    "org": "Omegatech LTD",
    "city": "Amsterdam",
    "country": "NL"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "hyperliquid-btc.com"
}
DNS records
{
    "A": [
        "130.12.180.154"
    ],
    "NS": [
        "c.dnspod.com",
        "a.dnspod.com",
        "b.dnspod.com"
    ],
    "SOA": "{\"nsname\": \"a.dnspod.com\", \"hostmaster\": \"domainadmin.dnspod.com\", \"serial\": 1792432780, \"refresh\": 3600, \"retry\": 180, \"expire\": 1209600, \"minttl\": 180}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "130.12.180.154",
    "family": 4
}
Tech stack
{
    "technologies": [
        "Nginx",
        "OpenResty"
    ]
}
Registration record
{
    "registrar": "Hosting Concepts B.V. d/b/a Registrar.eu",
    "created": "2026-10-19T17:22:40Z",
    "updated": "2026-10-19T17:22:43Z",
    "expires": "2027-10-19T17:22:40Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "a.dnspod.com",
        "b.dnspod.com",
        "c.dnspod.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "openresty",
        "content-type": "text/html"
    }
}
Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Gelistet View source
PhishDestroy PhishDestroy list View source
SEAL Gelistet View source

Last checked

Gespeicherte Aufnahme · 5 captures

Primary capture 1 / 5
QuellePrimary capture
Recorded2026-10-21 08:32 UTC
StateStored capture
HTTP status at archiveHTTP 200
Final URLhttps://hyperliquid-btc.com/
Position1 / 5
Open capture Wayback Herunterladen

Domain details

Domain
IP-Reputation abuse score 2/100 3 reports PhishingExploited Host checked 21.10.2026
OTX tags 2026-10activeall-domainsblocklistcontentcryptoDomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Hosting Concepts RO(RO)
Abuse-Kontaktabuse@registrar.eu
ICANN-RegistrierungsstelleICANN Lookup (RDAP) →
WHOIS-AbfrageICANN RDAP für hyperliquid-btc.com →
RegistrierungExpires 19.10.2027
HTTP-Status200
Technische DetailsProvenance & timestamps
Erstmals entdeckt21.10.2026
DOM Analysisanalyzed 21.10.2026score 10/1004 brand signals
Submitted URLhttp://hyperliquid-btc.com/
Favicon Hash
Fall-ID
Observed page title
Hyperliquid | Exchange Platform
Automated brand references
Ethereum Ledger Near Solana
TLS-Zertifikat
Ausgestellt von YE1 · stored validity ends in 89 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
130.12.180.154
Network ASN
AS202412
Organization
Omegatech LTD
Observed location
Amsterdam, NL
Server header
openresty

Nameserver 3

  • a.dnspod.com
  • b.dnspod.com
  • c.dnspod.com

Location describes the IP network.

TLS-Zertifikat

Issuer
YE1
Valid from
2026-10-20 17:34:44
Valid until
2027-01-18 17:34:43
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintffed0b2c76f31f655ff9a3c970b0cba8f61c29ebee2245fd7b4e08be855fb590
Certificate names · 2 SANs
  • hyperliquid-btc.com
  • www.hyperliquid-btc.com

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 130.12.180.154rapiddns.io

Latest Classified Outcome 2026-10-21 11:03:01 UTC

Primary outcome Aktive Inhalte reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Unreachable Content: Unknown DNS: Stale Registration: Unknown
Latest HTTP observation Aktive Inhalte Ordinary HTTP content served 90% 2026-10-21 11:03:01 UTC
RDAP registration Unbekannt
Observed timeline last reachable: 2026-10-21 08:32:56 UTC
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.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.hyperliquid-btc.comDomain record

The original observation time is not recorded for these hostnames.

Technologien · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Diese Domain melden Reichen Sie Beweismaterial ein und helfen Sie mit, andere zu schützen

VirusTotal-Analyse

4 / 92 Sicherheitsanbieter haben diese Domain markiert
View on VT
Last analyzed First positive detection Previous stored snapshot: 4 detections
alphaMountain.ai
Forcepoint ThreatSeeker
Fortinet
SOCRadar
Website-Performanceanalyse

Google PageSpeed Insights — mobile performance audit of hyperliquid-btc.com · checked Oct 21, 2026

85
Needs Work
Performance
FCP
3.32s
First Contentful Paint
LCP
3.32s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
3.32s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://hyperliquid-btc.com/
Final URL: https://hyperliquid-btc.com/
Hyperliquid | Exchange Platform
Hyperliquid DEX lands Pumpfun perps, files an SEC comment letter and keeps burning HYPE. Inside the Hyperliquid exchange, HIP-3 markets and the future of Hyperliquid crypto.
Reaktion
HTTP 200
HTML body
35.4 KB
Compressed
12.0 KB
Links
13 internal · 0 external
Selected response headers
Server: openresty
Content-Type: text/html
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Open Graph title: Hyperliquid | Exchange Platform
Open Graph description: Pump fun perps, an SEC letter and daily HYPE burns. Why the Hyperliquid exchange is setting the pace for decentralized trading in 2026.
Twitter card: summary_large_image
Saved response-header values · 9
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Wed, 21 Oct 2026 08:33:17 GMT
Etag
W/"6ad7b4eb-8d82"
Last-Modified
Tue, 20 Oct 2026 18:37:31 GMT
Server
openresty
Transfer-Encoding
chunked
Vary
Accept-Encoding

Values retained by the collector; long values may be shortened during collection.

Archived
Registration & observation details1

Availability observations

Last reachable observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history4

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. VirusTotal · Detection count

    3→4

  2. Availability monitor · Recorded state

    Unbekannt→live_content

    content_served

  3. VirusTotal · Detection count

    1→3

  4. Availability monitor · First collection record

    Erreichbar

Recorded activity

6 entries
  1. AlienVault OTX

    4 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    4/92 engine detections

    View source
  4. Abuse report sent

    PD-20261021-59AEAE

    abuse@registrar.eu
  5. Added to PhishDestroy

    hyperliquid-btc.com

    View source
  6. URLScan

    Page captured

    View source

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

hyperliquid-btc.com

Nachweise und externe Berichte

Sicherheitsanalyse
URLScan Stored capture VirusTotal 4 det. ChainPatrol URLQuery Report stored SSL Labore Stored certificate dates valid CF-Radar Bericht öffnen OTX 4 refs WOT ScamAdviser Blacklist-Prüfung URLVoid Sucuri SiteCheck MDN-Beobachtungsstelle
Momentaufnahme der übermittelten Beweise
Sent: Ledger records: 1 Case ID: PD-20261021-59AEAE Recipient: abuse@registrar.eu
Page title stored with report: Hyperliquid | Exchange Platform
PDF notice generated
OSINT und Nachrichtendienst
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Zertifikate WHOIS Wayback
DNS & Netzwerk
nslookup.io DNS bgp.tools ASN /Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Eingehende Analyse
Eingehende Analyse
Help & reporting

Wurden Sie von dieser Website betroffen?

6 evidence signal groups linked 1 stored notification records Letzter bekanntermaßen aktiv
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Wenn Sie Kontoanmeldeinformationen, persönliche oder Zahlungsinformationen eingegeben oder eine Datei von dieser Domain heruntergeladen haben, ergreifen Sie sofort Maßnahmen. Nachfolgend finden Sie Ressourcen, die Ihnen helfen, den Vorfall zu melden und sich zu schützen.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Kein Strafverfolgungsbericht
Domain-Einspruch
Fordern Sie eine Überprüfung an, wenn Sie Inhaber dieser Domain sind und der Meinung sind, dass der Eintrag falsch ist
Vorsicht vor Betrügern, die mit der Rückforderung von Geldern locken! Kriminelle nehmen unter Umständen erneut Kontakt zu Opfern auf und geben dabei vor, Ermittler, Anwälte oder Beitreibungsbeamte zu sein. Zahlen Sie keine Vorabgebühren und geben Sie keine Anmeldeinformationen weiter. Erfahren Sie mehr über Betrug im Zusammenhang mit Wiederaufbaumaßnahmen →

Melden Sie sich bei Ihren örtlichen Behörden

Wählen Sie Ihr Land aus, um Offizielle Kontakte im Bereich Cyberkriminalität oder einen Beschwerdeentwurf erstellen → zu erhalten.

97-Länder-Verzeichnis

Template-based draft · optional AI wording assistance requires separate consent

KI-gestützter Entwurf – Vorfalldetails werden vom KI-Anbieter verarbeitet · Überprüfen Sie es und reichen Sie es selbst ein
After a phishing incident

Empfehlungen und Ratschläge für Betroffene

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

Was soll ich sofort tun?

Dringend

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Alle Passwörter ändern — E-Mail, Exchange-Konten, alles, wofür dasselbe Passwort verwendet wird
  • 2FA aktivieren mit einer Authentifizierungs-App (nicht per SMS). Deaktivieren Sie die SMS-basierte Wiederherstellung
  • Karten einfrieren Falls Sie auf der Phishing-Seite Ihre Bankdaten eingegeben haben

Welche Informationen sollte ich für meinen Bericht sammeln?

FBI-Richtlinien

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Genaue Daten und Uhrzeiten — jeder Transaktion und des ersten Kontakts mit dem Betrüger
  • Screenshots — betrügerische Websites, Chat-Nachrichten, E-Mails, Wallet-Transaktionen, soziale Medien
  • Alle URLs und Domains die der Betrüger verwendet (einschließlich hyperliquid-btc.com)
  • Kommunikation — E-Mails, SMS, Telefonnummern, Benutzernamen, die der Betrüger verwendet hat

Auch wenn dir nicht alle Details bekannt sind — trotzdem Anzeige erstatten. Auch unvollständige Informationen sind für die Ermittlungen hilfreich.

Wo soll ich den Betrugsfall melden?

  • FBI IC3 — Internet Crime Complaint Center (Meldestelle der US-Bundesbehörden)
  • Europol — Meldungen zu Cyberkriminalität in Europa (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Ortspolizei — sorgt für eine offizielle Dokumentation, auch wenn sie nicht sofort handeln können

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Gefälschte Websites — pixelgenaue Kopien legitimer Websites mit leicht abgeänderten Domains
  • Schweineschlachtung — über Wochen hinweg über Telegram, WhatsApp und Dating-Apps aufgebautes Vertrauen, dann wurde Geld gestohlen
  • Betrugsmaschen im Zusammenhang mit der Rückforderung von Geldern — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Durch KI gestützte Betrugsmaschen — Deepfakes, automatisiertes Phishing und KI-generierte Websites, die es erschweren, Betrugsversuche zu erkennen

Wie kann ich mich in Zukunft schützen?

  • Offizielle Websites als Lesezeichen speichern — Klicken Sie niemals auf Links in E-Mails, Direktnachrichten oder Anzeigen
  • Domains überprüfen — nachsehen, ob PhishDestroy Bevor Sie Kontakt aufnehmen: Überprüfen Sie HTTPS, die Rechtschreibung und das Alter der Domain.
  • „Zu schön, um wahr zu sein“ = Betrug — garantierte Renditen, Prominente als Werbeträger, dringende Fristen

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Jede beliebige Domain prüfen

Bedrohungsanalyse anhand gespeicherter Blocklisten, WHOIS, DNS und öffentlicher Scan-Beweise

Jetzt scannen

Phishing melden

Melden Sie verdächtige Domains an unsere Bedrohungsdatenbank – schützen Sie die Community

Melden

Echtzeit-Bedrohungsfeed

Aktuelle Phishing-Meldungen und beobachtete Verfügbarkeitsänderungen

Überwachen

Bleiben Sie auf dem Laufenden, bleiben Sie sicher

Beobachten Sie aktuelle Bedrohungen oder legen Sie Widerspruch gegen diesen Eintrag ein, wenn Sie der Meinung sind, dass es sich um einen Fehlalarm handelt

Echtzeit-Bedrohungsfeed Einspruch gegen diesen Eintrag einlegen
About this reportSources, observation dates and corrections

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.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Diesen Bericht einbetten

Teilen Sie diese Bedrohungsinformationen auf Ihrer Website oder in Ihrem Blog

embed.html 
<iframe
  src="https://phishdestroy.io/de/embed/domain/hyperliquid-btc.com"
  title="PhishDestroy threat report for hyperliquid-btc.com"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>