Sicherheits-Engines melden eine Entdeckung: 19. Öffentliche Blocklisten, die eine Übereinstimmung melden: 2. Seien Sie äußerst vorsichtig – Geben Sie keine Anmeldeinformationen oder persönlichen Daten ein.
Berichtsübersicht
global-app.to — Letzter bekanntermaßen aktiv (HTTP 301). Markenidentität: Ethereum; Betrugstyp: Impersonation. Zusammenfassung der Beweislage: VirusTotal 19/89 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar); Spamhaus DBL_PHISH; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 100/100. Registrar: Government of Kingdom ….
Die ausführliche Analyse von PhishDestroy AI bleibt auf Englisch, damit der ursprüngliche forensische Bericht unverändert bleibt.
Stored evidence for global-app.to: VirusTotal recorded 19 detections among 89 scanners on 2026-09-20. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for global-app.to. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 19 detections among 89 scanners in the stored snapshot dated 2026-09-20. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-20 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
Source Context
MetaMask and SEAL are recorded as named external blocklist observations for global-app.to in the snapshot dated 2026-09-20. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains global-app.to as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
Reachability and Timeline
The record first observed global-app.to on 2026-09-13. The MetaMask and SEAL blocklist snapshot is dated 2026-09-20 and remains a separate event in the stored timeline. A stored HTTP status 404 was observed for global-app.to on 2026-09-20. The HTTP status 404 dated 2026-09-20 records a single response for later comparison. The registration date is separately recorded as 2026-04-20. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
Registration and Infrastructure
For global-app.to, the registrar field records Government of Kingdom of Tonga; this is kept as an exact source value. The source stores 172.67.142.243 as the observed address in this record. The registration date for global-app.to is recorded as 2026-04-20. The SSL issuer is recorded as Let's Encrypt / YE2 in the snapshot dated 2026-09-19. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
Conclusion
The global-app.to record states that VirusTotal recorded 19 detections among 89 scanners on 2026-09-20. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-20. PhishDestroy remains a separate publisher catalogue entry in the stored record. For global-app.to, the registrar field records Government of Kingdom of Tonga; this remains separate from the other source fields. The observed address field in this record contains 172.67.142.243. The supported conclusion is bounded to the exact stored observations for global-app.to. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to global-app.to during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain global-app.to as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to global-app.to. The stored record does not justify extending that rule to 172.67.142.243 or to other infrastructure records.
Analyse von Erkennung und Umgehung
Verdacht auf Cloaking: Scanner- und Besuchertitel weichen voneinander ab
Noch nicht eingescanntBislang wurde noch kein Unterschied zwischen Crawler und Browser festgestellt.
Gespeicherte Beobachtungen zum Vergleich zwischen Crawler und Browser für diesen Host sowie eine Echtzeit-Fingerabdruckprüfung für Verkehrsverteilungssysteme im Keitaro-Stil.
Gespeichertes Cloaking-Flag
Noch nicht eingescannt
Letzter Tarnungsscan
Vom Scanner erkannter Server-Header
cloudflare
Anmerkung des Scanners:redirect: raw=redirect_301; http=301; via=http_proxy; location=https://global-app.to/; server=cloudflare
Titel, der dem Sicherheitsscanner angezeigt wird301 Moved Permanently
Titel, der einem Browser-Besucher angezeigt wirdSwap | Sushi 🍣
Live-TDS-Fingerabdruckprüfung
Sieben Keitaro-Fingerabdrücke sowie ein Vergleich zwischen Crawler und Browser, der vom „PhishDestroy“-Scanner ausgeführt wird, wenn dieses Fenster geöffnet ist.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-13 10:07:32 UTC
RDAP registrationUnbekannt
Observed timelinelast reachable: 2026-10-13 10:07:32 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.
Technologien · 2 identified
Cloudflare
CDN
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Last analyzed First positive detection Previous stored snapshot: 18 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
Fortra
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Webroot
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-10-09 01:42:50 UTC
Domain state transitioned from dead to alive.
VirusTotal Detections Update2026-09-20 19:44:00 UTC
VirusTotal scanner detections updated from 18 to 19. Added scanner alerts: SOCRadar.
Domain ingestion complete. Initial state is marked as alive.
Pipeline zur Reaktion auf Sicherheitsbedrohungen
Entdeckung
Analysis
Monitoring
15 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Bedrohung erkannt
global-app.to erkannt und für eine vollständige Analyse in die Warteschlange gestellt
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Die Domäne bleibt erreichbar oder zugriffsbeschränkt; Zukünftige Überprüfungen könnten diese Beobachtung aktualisieren.
How we investigate & report
Public scans, evidence and abuse channels
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
Dear Team,
We are writing to report a phishing website operating at global-app[.]to. It was built to impersonate the SushiSwap crypto exchange and to steal cryptocurrency from the people who go looking for it.
It is a phishing redirect from global-app[.]to to sushi[.]com-vivid-
1 report filed for global-app.to (1 written by a person) · category: Phishing · source checked
“Dear Team,
We are writing to report a phishing website operating at global-app[.]to. It was built to impersonate the SushiSwap crypto exchange and to steal cryptocurrency from the people who go looking for it.
It is a phishing redirect from global-app[.]to to sushi[.]com-vivid-web[.]bond. The domain is indexed under the SushiSwap name, and not as one page — a whole "SushiSwap Exchange" section stands under it, complete with its own disclaimer, a cookie policy and tens of thousands of invented”
— reported by Anonymous on Sep 12, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
4 evidence signal groups linked0 reports recordedLetzter 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.
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 →
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
Verwandte Infrastruktur und Berichte
Gespeicherte Beziehungen werden nach dem genau passenden Attribut gruppiert. Ein gemeinsam genutzter Anbieter oder Registrar allein beweist keinen gemeinsamen Besitz.
Direkter Link Verwendet eine Registrierung oder ein identisches Phishing-Kit.
Hilfssignal Gemeinsame Nutzung der Infrastruktur oder einer Zielmarke; kein Hinweis auf einen einzigen Betreiber.
Nur zur Einsicht Zur Navigation aufgeführt; keine gemeinsamen Attribute mit diesem Host.
Infrastrukturkarte · global-app.to
Jede Spalte gibt einen Grund an, warum eine Domain mit diesem Host verknüpft ist. Knoten in voller Größe kennzeichnen „VirusTotal“-Erkennungen, gestrichelte Knoten sind bereits offline. Die vollständigen Listen folgen weiter unten.
Inhaltliche Übereinstimmungen8
Derselbe Favicon-Hash oder derselbe Seitentitel wie bei diesem Host.
Weitere Berichte zur gemeinsamen Nutzung von Cloudflare Edge2
Diese Berichte werden auf dieselbe gemeinsame Edge-IP aufgelöst. Sie helfen bei der Berichtserkennung, bedeuten jedoch keinen gemeinsamen Besitz oder einen gemeinsamen Ursprungsserver.
Über denselben Registrar registriert. Ein Registrar betreut Millionen von Kunden, die in keiner Verbindung zueinander stehen; daher werden hier lediglich Berichte zusammengefasst, anstatt eine Verbindung nachzuweisen.
Beobachten Sie aktuelle Bedrohungen oder legen Sie Widerspruch gegen diesen Eintrag ein, wenn Sie der Meinung sind, dass es sich um einen Fehlalarm handelt
(TO)
