card-metamask.com
“card-metamask.com”
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@internet.bs.
The latest stored availability evidence still shows the domain reachable; 6 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
card-metamask.com — Erreichbar · Zugang eingeschränkt (HTTP 403). Markenidentität: MetaMask; Betrugstyp: Impersonation. Zusammenfassung der Beweislage: VirusTotal 17/89 (ChainPatrol, alphaMountain.ai, BitDefender, Certego, CRDF); URLQuery 3 alerts; URLScan malicious verdict; 4 external blocklist matches; PhishDestroy score 100/100. Registrar: Internet Domain Servic….
Die ausführliche Analyse von PhishDestroy AI bleibt auf Englisch, damit der ursprüngliche forensische Bericht unverändert bleibt.
Zusammenfassung der Beweislage
Assessment
Stored evidence for card-metamask.com: VirusTotal recorded 17 detections among 89 scanners on 2026-09-13. That ratio reproduces the stored check in its original units and is not converted into another measure. ScamSniffer, Enkrypt, and PhishFeed appear as named external blocklist observations for card-metamask.com. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 17 detections among 89 scanners in the stored snapshot dated 2026-09-13. 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-13 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
ScamSniffer, Enkrypt, and PhishFeed are recorded as named external blocklist observations for card-metamask.com in the snapshot dated 2026-09-13. The stored ScamSniffer, Enkrypt, and PhishFeed blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains card-metamask.com as a publisher record. That PhishDestroy record is counted separately from the ScamSniffer, Enkrypt, and PhishFeed 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 card-metamask.com on 2026-09-13. The ScamSniffer, Enkrypt, and PhishFeed blocklist snapshot is dated 2026-09-13 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-07-07. 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 card-metamask.com, the registrar field records Internet Domain Service BS Corp; this is kept as an exact source value. The source stores 172.67.135.248 as the observed address in this record. The registration date for card-metamask.com is recorded as 2026-07-07. 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 card-metamask.com record states that VirusTotal recorded 17 detections among 89 scanners on 2026-09-13. ScamSniffer, Enkrypt, and PhishFeed remain named blocklist observations from the snapshot dated 2026-09-13. PhishDestroy remains a separate publisher catalogue entry in the stored record. For card-metamask.com, the registrar field records Internet Domain Service BS Corp; this remains separate from the other source fields. The observed address field in this record contains 172.67.135.248. The supported conclusion is bounded to the exact stored observations for card-metamask.com. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to card-metamask.com during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain card-metamask.com as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and ScamSniffer, Enkrypt, and PhishFeed 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 card-metamask.com. The stored record does not justify extending that rule to 172.67.135.248 or to other infrastructure records.
Erkenntnisse zur Netzwerksicherheit
Forensic History & Detection Timeline
-
Domain Status Transition Sep 19, 2026 · 04:17 UTCDomain state transitioned from alive to dead.
-
Threat First Observed Sep 13, 2026 · 20:20 UTCDomain ingestion complete. Initial state is marked as unknown pointing to IP
172.67.135.248.
Pipeline zur Reaktion auf Sicherheitsbedrohungen
Status der öffentlichen Sperrliste
Evasion analysis
Cloaking suspected: scanner and victim titles differ
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
- Stored cloaking flag
- Not yet scanned
- Last cloaking scan
- Server header seen by scanner
cloudflare
Scanner note: cloudflare_ban: raw=cf_phishing_block; http=403; via=https_direct; server=cloudflare; provider_error=cloudflare_phishing_interstitial
Provider response during scan: cloudflare_phishing_interstitial
Technologien · 8 identified
VirusTotal-Analyse
Website-Performanceanalyse
Google PageSpeed Insights — mobile performance audit of card-metamask.com · checked Sep 13, 2026
Ähnliche Domains
79 gespeicherte ähnliche Domains
Alle anzeigen (67)
Community-Erkenntnisse
2 Community-Meldungen
KategoriePHISHING
@drainer Telegram
Nachweise und externe Berichte
“@drainer Telegram”
PD-20260913-BC90F2 Recipient: abuse@internet.bs Abuse notice text as sent to the provider
Policy Violations: Illegal Activities: Active phishing operation targeting victims Fraud & Deception: Impersonation of legitimate services Identity Theft: Collection of credentials under false pretenses Applicable Laws (BS): International Anti-Cybercrime Regulations Budapest Convention on Cybercrime Universal Fraud Prevention Laws Phishing activities violate international cybercrime conventions and BS's domestic fraud laws. Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
Wurden Sie von dieser Website betroffen?
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.
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.
Jede beliebige Domain prüfen
Bedrohungsanalyse anhand gespeicherter Blocklisten, WHOIS, DNS und öffentlicher Scan-Beweise
Jetzt scannenPhishing melden
Melden Sie verdächtige Domains an unsere Bedrohungsdatenbank – schützen Sie die Community
MeldenEchtzeit-Bedrohungsfeed
Aktuelle Phishing-Meldungen und beobachtete Verfügbarkeitsänderungen
ÜberwachenBleiben 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