VirusTotal
15 / 89
DenunciarEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Track”
Assessment based on the stored source evidence below. Review sources →
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@omegatech.sc.
The latest stored availability evidence still shows the domain reachable; 1 month 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.
upservice-dienst.net — Último activo conocido (HTTP 301). Suplantación de marca: MetaMask; Tipo de estafa: Impersonation. Resumen de las pruebas: VirusTotal 15/89 (alphaMountain.ai, BitDefender, CRDF, ESET, Emsisoft); URLQuery 2 alerts; Spamhaus DBL_PHISH; 2 external blocklist matches (MetaMask, SEAL); CF Radar malicious; PhishDestroy score 100/100. Registrador: Cloudflare.
El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
15 / 89
DenunciarEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
2 threat-system alerts
DenunciarAlerts refer to the preserved scan. They do not describe the current state of the site.
provider verdict: malicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
2 external matches
DetallesA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
DBL_PHISH
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
4 community references
DenunciarCommunity publication references, not a vendor verdict or evidence of a common operator.
informe almacenado
View stored capture ↗ DenunciarA preserved page image documents what the collector received; a capture is not a safety verdict.
Análisis finalizado
DenunciarThis is the recorded automated analysis. Completion alone is not a safety verdict.
80/100
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Checked; no threat flag recorded
DenunciarA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.
Stored evidence for upservice-dienst.net: VirusTotal recorded 10 detections among 90 scanners on 2026-09-06. 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 upservice-dienst.net. Each item in this report remains at the scope supplied by its dated source record.
VirusTotal records 10 detections among 90 scanners in the stored snapshot dated 2026-09-06. 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-06 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 upservice-dienst.net in the snapshot dated 2026-09-05. 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 upservice-dienst.net 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 upservice-dienst.net on 2026-09-05. The MetaMask and SEAL blocklist snapshot is dated 2026-09-05 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-09-04. A URLScan reference was stored on 2026-09-05 as a dated artifact for review. 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 upservice-dienst.net, the registrar field records Cloudflare, Inc.; this is kept as an exact source value. The source stores 158.94.208.174 as the observed address in this record. The registration date for upservice-dienst.net is recorded as 2026-09-04. The SSL issuer is recorded as Let's Encrypt / YR2 in the snapshot dated 2026-09-05. The observed server header is recorded as nginx in this record. 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 upservice-dienst.net record states that VirusTotal recorded 10 detections among 90 scanners on 2026-09-06. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-05. PhishDestroy remains a separate publisher catalogue entry in the stored record. For upservice-dienst.net, the registrar field records Cloudflare, Inc.; this remains separate from the other source fields. The observed address field in this record contains 158.94.208.174. The supported conclusion is bounded to the exact stored observations for upservice-dienst.net. Any statement beyond those source values would require additional dated material.
Avoid submitting sensitive information to upservice-dienst.net during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain upservice-dienst.net 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 upservice-dienst.net. The stored record does not justify extending that rule to 158.94.208.174 or to other infrastructure records.
23 · datasets with records / 8 · not recorded
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
2 · external source matches
Cloudflare, Inc. · 158.94.208.174 · DNS, TLS and retained responses
La reputación de Edge-IP no se atribuye a este dominio.
anita.ns.cloudflare.comclark.ns.cloudflare.comLocation describes the IP network.
e048b424cf121d873f4e6b56879303e342d0805e23e77df3fe67f3e3492b228aSaved 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 upservice-dienst.net · checked Sep 5, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored browser and crawler observations
Observaciones almacenadas de rastreadores frente a navegadores para este servidor, además de una comprobación en tiempo real de la huella digital para sistemas de distribución de tráfico al estilo Keitaro.
nginxNota del escáner: redirect: raw=redirect_301; http=301; via=http_proxy; location=https://upservice-dienst.net/; server=nginx
1 · outbound report records
158.94.208.174.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Desconocido→redirected
http_redirect
redirected→Desconocido
probe_inconclusive
Desconocido→redirected
http_redirect
redirected→Desconocido
probe_inconclusive
Desconocido→redirected
http_redirect
redirected→Desconocido
probe_inconclusive
Desconocido→redirected
http_redirect
redirected→Desconocido
probe_inconclusive
Desconocido→redirected
http_redirect
redirected→Desconocido
probe_inconclusive
Desconocido→redirected
http_redirect
redirected→Desconocido
probe_inconclusive
Desconocido→redirected
http_redirect
redirected→Desconocido
probe_inconclusive
Desconocido→redirected
http_redirect
redirected→Desconocido
probe_inconclusive
Desconocido→redirected
http_redirect
redirected→Desconocido
probe_inconclusive
Desconocido→redirected
http_redirect
redirected→Desconocido
probe_inconclusive
redirected→Desconocido
stale_current_evidence
Desconocido→redirected
http_redirect
Desconocido→redirected
http_redirect
redirected→Desconocido
probe_inconclusive
Desconocido→redirected
http_redirect
redirected→Desconocido
probe_inconclusive
Desconocido→redirected
http_redirect
Desconocido
probe_inconclusive
Accesible
14 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.
Shared hosting, registrar records and related domains
79 dominios similares almacenados
Original reports, independent checks and evidence links
PD-20260905-B14BB4 Recipient: abuse@omegatech.sc 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 (FR): French Penal Code Article 323-1 French Penal Code Article 313-1 (Fraud) Law for a Digital Republic French law prohibits fraudulent access to automated data processing systems. 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.
Recovery steps, reporting contacts and complaint drafts
Si ingresó credenciales de cuenta, información personal o de pago, o descargó un archivo de este dominio, tome medidas inmediatas. A continuación encontrará recursos que le ayudarán a informar el incidente y protegerse.
Seleccione su país para obtener contactos oficiales de cibercrimen o crear un borrador de queja →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
upservice-dienst.net)Aunque no tengas todos los detalles — presenta la denuncia de todos modos. Incluso la información parcial sigue siendo útil para las investigaciones.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Análisis de amenazas utilizando listas de bloqueo almacenadas, WHOIS, DNS y evidencia de escaneo público
Escanear ahoraEnvía los dominios sospechosos a nuestra base de datos de amenazas: protege a la comunidad
DenunciarInformes de phishing recientes y cambios de disponibilidad observados
MonitorizarSupervisa las amenazas en tiempo real o impugna esta entrada si crees que se trata de un falso positivo.
Este informe presenta la última evidencia almacenada disponible para PhishDestroy. Las marcas de tiempo de origen se muestran cuando están disponibles; La disponibilidad y los veredictos de los proveedores pueden cambiar después de la recolección.
El sitio capturado mostraba el título de la página “Track” y puede estar haciéndose pasar por MetaMask.
A partir de 2026-09-13 02:11:08 UTC, upservice-dienst.net tuvo detecciones de los motores de seguridad 15.
Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.
Si cree que esta lista es inexacta, presentar una apelación. Para conocer nuestra metodología, visita el Página de preguntas frecuentes.