Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@vercel.com.
The latest stored availability evidence still shows the domain reachable; 27 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.
tuw-mujab[.]com
Phishing- und Sicherheitsprüfung für tuw-mujab.com
“Trust Card”
tuw-mujab.com — Letzter bekanntermaßen aktiv (HTTP 308). Zusammenfassung der Beweislage: VirusTotal 1/91 (alphaMountain.ai); URLQuery 2 alerts; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 83/100. Registrar: Name.com.
Die ausführliche Analyse von PhishDestroy AI bleibt auf Englisch, damit der ursprüngliche forensische Bericht unverändert bleibt.
The domain tuw-mujab.com was registered on July 12, 2026 through Name.com, Inc. and is currently resolving to the IPv4 address 216.150.16.1. The domain is delegated to the authoritative name servers ns1.vercel-dns.com and ns2.vercel-dns.com, which are typical of a cloud‑based hosting provider. As of the report date the domain remains active.
Initial threat intelligence classifies the domain as a generic_phishing infrastructure. No publicly available samples have yet triggered detections on VirusTotal, resulting in a 0/95 detection count. The lack of detections does not imply benign intent, and the rapid creation‑to‑activation timeline is consistent with opportunistic phishing campaigns that rely on short‑lived domains.
Infrastructure analysis shows a single hosting IP, 216.150.16.1, which is not currently associated with known malicious repositories. However, the use of a shared DNS service and a generic cloud host can facilitate rapid redeployment of malicious pages. The registrar information provides no indication of anonymization, suggesting the operator may be leveraging a legitimate registration to reduce immediate scrutiny.
Defenders should consider adding the resolved IP address and the domain name to blocklists and monitoring egress traffic for connections to the host. Continuous DNS monitoring is recommended to detect any changes to the name server configuration or additional IP addresses that may be introduced. Further investigation of web content served from the host, including HTTP headers and page content, is advisable to confirm the phishing payload.
Organizations that use brand‑specific authentication portals should educate users to verify URLs and implement multi‑factor authentication to limit credential compromise. Incident response teams should preserve any captured network artifacts and submit them to shared analysis platforms to enrich community knowledge of this emerging campaign.
Erkenntnisse zur Netzwerksicherheit
Pipeline zur Reaktion auf Sicherheitsbedrohungen
Status der öffentlichen Sperrliste
Gespeicherte Aufnahme
Domain-Intelligenz
Technische DetailsDNS, SSL-SANs, Zeitstempel
ICANN OVERSIGHT
Akkreditierung und RAA-Kontext
Akkreditierung und RAA-Kontext
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
Technologien · 2 identified
Vercel is a cloud platform for static frontends and serverless functions.
vercel.com 100 % KonfidenzHTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
www.rfc-editor.org 100 % KonfidenzVirusTotal-Analyse
Nachweise und externe Berichte
PD-20260712-A2EE2C Recipient: abuse@vercel.com 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