uphuligin[.]github[.]io
Análisis de phishing y seguridad de uphuligin.github.io
“Uph𝓸ld Login | Login | SignUp”
US
Suplantación de identidad para obtener credenciales
+ more
uphuligin.github.io: VirusTotal registra 11 detecciones de 95. Consulta DNS, SSL, registrador, listas de bloqueo y datos sobre amenazas.
El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.
PhishDestroy first recorded uphuligin.github.io on Oct 28, 2025. This English evidence brief is rebuilt from the current structured observations stored for the report. The current stored risk score is 83/100.
The latest stored availability state is “Content unavailable” (HTTP 404) on Aug 1, 2026 at 03:07 UTC. This is a reachability snapshot, not proof of the cause of any outage, restriction, or status change.
VirusTotal returned 11 detections from 95 scanners in the stored check on Jul 18, 2026 at 20:45 UTC. The independent blocklist snapshot recorded 0 matches across 10 configured external sources on Aug 2, 2026 at 00:20 UTC. PhishDestroy's own listing is excluded from that count. A zero-match snapshot is not a safety verdict.
Other stored evidence. Google Safe Browsing stored no positive flag on Mar 3, 2026 at 05:14 UTC. This time-bound result is not evidence of safety. AlienVault OTX stored 0 pulse references on Mar 1, 2026 at 20:14 UTC. OTX pulses are community-intelligence references, not vendor verdicts. The Spamhaus DBL snapshot stored no positive result on Jul 14, 2026 at 20:35 UTC. That result is not evidence of safety. A URLScan capture is stored from Mar 3, 2026 at 02:17 UTC.
Stored context lists registrar GitHub, Inc., IP address 185.199.110.153, apparent target Uphold. Except for the registration date, these fields do not share a source timestamp in this report and may change.
Treat these as stored, time-bound observations rather than a live safety guarantee. Source verdicts and reachability can change, and zero or missing vendor matches never prove that a domain is safe. Avoid interacting with the domain while uncertainty remains, and use the appeal process if this report is inaccurate.
