VirusTotal
7 / 89
“PHANTOM V2”
phantomv2.pro — Inhalt nicht verfügbar. Markenidentität: Phantom; Betrugstyp: Crypto Drainer; Drainer: Solana Drainer. Zusammenfassung der Beweislage: VirusTotal 7/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft); URLQuery 1 alert; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 100/100. Registrar: Hostinger.
Die ausführliche Analyse von PhishDestroy AI bleibt auf Englisch, damit der ursprüngliche forensische Bericht unverändert bleibt.
7 / 89
1 threat-system alert
Melden15/100
Meldenno community references
Meldenprovider verdict: clean
Meldengespeicherter Bericht
Melden Analyse abgeschlossen
MeldenChecked; no threat flag recorded
Melden| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | phantomv2.pro |
malicious | Sinkholed |
Stored evidence for phantomv2.pro: VirusTotal recorded 2 detections among 89 scanners on 2026-09-11. 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 phantomv2.pro. Each item in this report remains at the scope supplied by its dated source record.
VirusTotal records 2 detections among 89 scanners in the stored snapshot dated 2026-09-11. 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-11 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.
MetaMask and SEAL are recorded as named external blocklist observations for phantomv2.pro in the snapshot dated 2026-09-11. 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 phantomv2.pro 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.
The record first observed phantomv2.pro on 2026-09-11. The MetaMask and SEAL blocklist snapshot is dated 2026-09-11 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-09-10. 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.
For phantomv2.pro, the registrar field records HOSTINGER operations, UAB; this is kept as an exact source value. The source stores 92.113.16.248 as the observed address in this record. The registration date for phantomv2.pro is recorded as 2026-09-10. 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.
The phantomv2.pro record states that VirusTotal recorded 2 detections among 89 scanners on 2026-09-11. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-11. PhishDestroy remains a separate publisher catalogue entry in the stored record. For phantomv2.pro, the registrar field records HOSTINGER operations, UAB; this remains separate from the other source fields. The observed address field in this record contains 92.113.16.248. The supported conclusion is bounded to the exact stored observations for phantomv2.pro. Any statement beyond those source values would require additional dated material.
Avoid submitting sensitive information to phantomv2.pro during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain phantomv2.pro 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 phantomv2.pro. The stored record does not justify extending that rule to 92.113.16.248 or to other infrastructure records.
Gespeicherte Beobachtungen zum Vergleich zwischen Crawler und Browser für diesen Host sowie eine Echtzeit-Fingerabdruckprüfung für Verkehrsverteilungssysteme im Keitaro-Stil.
Anmerkung des Scanners: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='phantomv2.pro', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("
artemis.dns-parking.comhermes.dns-parking.comLocation describes the IP network.
cda8c8f61fd87b0fe93cca68c0291b9283e14ba2105f885bd33f32ad80df1963www.phantomv2.proSaved 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 phantomv2.pro · checked Sep 11, 2026
88.222.222.255. 13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
3 gespeicherte ähnliche Domains
PD-20260911-10AE38 Recipient: abuse@hostinger.com Registrar: Hostinger Operations UAB (Lithuania (EU)) Policy Violations: AUP prohibits illegal activity including fraud, phishing, malware hosting; Hostinger may suspend/terminate services and domains Applicable Laws: Lithuanian Criminal Code (Ch. XXX, §§196–198 data/system crimes; §§214–215 electronic fraud); EU Directive 2013/40/EU
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
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
Schätzungsweise $51 billion flossen im Jahr 2024 in illegale Krypto-Wallets (source). Falls Sie mit phantomv2.pro — Handeln Sie jetzt.
Laut der FBI, wobei die wichtigsten Angaben die Transaktionsdaten sind:
0x5856...35985)phantomv2.pro)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.