Ir al informe de seguridad
Domain security report
upservice-dienst.net favicon

upservice-dienst.net

“Track”

Veredicto de amenaza
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Disponibilidad Último activo conocido Última observación de accesibilidad almacenada Observado · HTTP probe
VirusTotal detecciones: 15/89 Spamhaus DBL: DBL_PHISH Coincidencias de la lista de bloqueo almacenadas: 2 URLQuery threat systems: 2 alerts Automated brand label: MetaMask
OTX: 4 refs 05/09/2026 MetaMask 1 Report Sent CDN
API
Registrador
Cloudflare
Resolved IP
158.94.208.174
Registered
04/09/2026
3 sources
In this reportGet help
Este dominio ha sido señalado como malicioso
Motores de seguridad que informan una detección: 15. Listas de bloqueo públicas que informan una coincidencia: 2. Tenga extrema precaución: no ingrese credenciales o información personal.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

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.

Elapsed since first report
1 month
Reports sent
1
Latest case ID
PD-20260905-B14BB4
Current status
HTTP 301 at latest stored check
Resumen del informe

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.

Additional indicators at a glance

Spamhaus DBL
DBL_PHISH
VirusTotal
VirusTotal
15 det.
URLQuery
URLQuery
2 threat alerts
OTX references
CF Radar
Malicioso
URLScan
URLScan
ScamAdviser
Scamadviser
80/100Likely Safe
Certificado TLS
Within stored validity dates
Let's Encrypt · Hostname coverage not recorded
Edad
1 mo New
Estado observado
Último activo conocido 301
PhishDestroy
DestroyList
Incluido
Reports Sent
1

Source evidence

10 · sources

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.

VirusTotal

15 / 89

Denunciar
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

URLQuery

2 threat-system alerts

Denunciar
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

CF Radar

provider verdict: malicious

Observation time not recorded
Denunciar
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Public blocklists

2 external matches

Detalles
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Spamhaus DBL

DBL_PHISH

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

4 community references

Denunciar
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

URLScan capture

informe almacenado

View stored capture ↗
Denunciar
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Análisis finalizado

Denunciar
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Scamadviser

80/100

Observation time not recorded
Denunciar
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Google Safe Browsing

Checked; no threat flag recorded

Denunciar
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Inteligencia de seguridad de red
Threat Detection Systems 2 alerts
Detection System Indicator Verdict Alert
OpenDNS upservice-dienst.net phishing Phishing Block
DNS4EU upservice-dienst.net malicious Sinkholed
CF Cloudflare Radar Verdict Malicioso
Phishing

Resumen de las pruebas

Crítico
VirusTotal
15/89
OTX
4 community refs
URLScan
Stored capture

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.

Assessment

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.

Detection Evidence

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.

Source Context

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.

Reachability and Timeline

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.

Registration and Infrastructure

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.

Conclusion

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.

Recommended Actions

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.

Data coverage & collection

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.

Recorded dataPartial recordUTC
VirusTotal
15 / 89 · engine detections
URLScan analysis
Automated verdict retained
URLQuery
2 · recorded detections / alerts
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
4 · community references
External blocklists
2 · external matches
Cloudflare Radar
maliciousCollection time not recorded
Scamadviser
80/100 · provider trust scoreCollection time not recorded
Spamhaus DBL
DBL_PHISH
Domain registration
Cloudflare, Inc.Collection time not recorded
Network & DNS
158.94.208.174 · 2 · nameserversCollection time not recorded
Certificado TLS
Let's Encrypt
Page captures
3 · retained captures
Page analysis
1 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
55/100 · mobile performance
Response records
1 · outgoing report records
Availability history
28 · stored state changes
Source observation history
1 · stored source events
Lookalike relationships
79 · retained relationshipsCollection time not recorded
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 8

These checks have no retained result. This does not mean they passed or that a scan is running.

  • PhishStats
  • DNS security filters
  • Gridinsoft
  • HTML archives
  • Site configuration files
  • Recorded subdomains
  • Reportes de la comunidad
  • Chainabuse records
Download the dated observations and supporting metadata.

Blocklist records

2 · external source matches

Estado de la lista de bloqueados pública

Domain, network & archive

Cloudflare, Inc. · 158.94.208.174 · DNS, TLS and retained responses

Domain details

Dominio
URLScan verdict Análisis finalizado score 0 report ↗
IP Context Sucuri shared edge origin IP hidden La reputación de Edge-IP no se atribuye a este dominio.
OTX tags 2026-09activeall-domainsblocklistcontentcryptodominiosdrainerfraudlivemonthlyphishdestroyphishingscam
Registrador Cloudflare FR(FR)
Contacto de abusoabuse@omegatech.sc
Registro de la ICANNICANN Lookup (RDAP) →
RegistroCreado 04/09/2026 (41d · New) — Expires 04/09/2027
Estado HTTP301 Moved Permanently
Detalles técnicosProvenance & timestamps
Primera detección05/09/2026
DOM Analysisanalyzed 05/09/2026score 100/1001 brand signal
Submitted URLhttp://upservice-dienst.net/
Favicon Hash
ID del caso

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
158.94.208.174
Network ASN
AS30148
Organization
SUCURI-SEC - Sucuri, US
Observed location
Menifee, US
Server header
nginx

La reputación de Edge-IP no se atribuye a este dominio.

Servidores de nombres 2
  • anita.ns.cloudflare.com
  • clark.ns.cloudflare.com

Location describes the IP network.

Certificado TLS

Issuer
Let's Encrypt
Valid from
2026-09-04 14:27:51
Valid until
2026-12-03 14:27:50
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-10 22:03:31 UTC
Collection source
PhishDestroy collector
Certificate fingerprinte048b424cf121d873f4e6b56879303e342d0805e23e77df3fe67f3e3492b228a

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-16 10:34:11 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-16 10:34:11 UTC
RDAP registration Desconocido
Observed timeline last reachable: 2026-10-16 10:34:11 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Tecnologías · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Denunciar este dominio Envía pruebas y ayuda a proteger a los demás

Análisis de VirusTotal

15 / Los proveedores de seguridad de 89 marcaron este dominio
View on VT
Last analyzed First positive detection Previous stored snapshot: 10 detections
alphaMountain.ai
BitDefender
CRDF
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Netcraft
SOCRadar
Sophos
Webroot

Evidencias archivadas

Wayback Machine Snapshot
Una instantánea histórica está disponible para revisión de evidencia.
View Archive
Análisis del rendimiento del sitio

Google PageSpeed Insights — mobile performance audit of upservice-dienst.net · checked Sep 5, 2026

55
Needs Work
Performance
FCP
8s
First Contentful Paint
LCP
14.3s
Largest Contentful Paint
CLS
0.093
Cumulative Layout Shift
TBT
52ms
Total Blocking Time
SI
8s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checks

Stored browser and crawler observations

Análisis de detección y evasión

Se sospecha que se está utilizando «cloaking»: los títulos del escáner y del visitante no coinciden

Aún no se ha escaneado Aún no se ha registrado ninguna diferencia entre los rastreadores y los navegadores

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.

Indicador de camuflaje almacenado
Aún no se ha escaneado
Último escaneo de camuflaje
Encabezado del servidor detectado por el escáner
nginx

Nota del escáner: redirect: raw=redirect_301; http=301; via=http_proxy; location=https://upservice-dienst.net/; server=nginx

Título que se muestra en el escáner de seguridad301 Moved Permanently
Título que se muestra al visitante del navegadorTrack
Comprobación de huellas dactilares en directo en TDS
Siete indicadores de Keitaro y una comparación entre navegador y rastreador. El análisis comienza solo al pulsar el botón.
Resultado guardado
Cloaked / Filtered

Timeline & response

1 · outbound report records

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. Threat First Observed 2026-09-05 14:44:13 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 158.94.208.174.
Stored observation history29

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  2. Availability monitor · Recorded state

    redirected→Desconocido

    probe_inconclusive

  3. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  4. Availability monitor · Recorded state

    redirected→Desconocido

    probe_inconclusive

  5. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

Earlier observations 24
  1. Availability monitor · Recorded state

    redirected→Desconocido

    probe_inconclusive

  2. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  3. Availability monitor · Recorded state

    redirected→Desconocido

    probe_inconclusive

  4. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  5. Availability monitor · Recorded state

    redirected→Desconocido

    probe_inconclusive

  6. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  7. Availability monitor · Recorded state

    redirected→Desconocido

    probe_inconclusive

  8. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  9. Availability monitor · Recorded state

    redirected→Desconocido

    probe_inconclusive

  10. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  11. Availability monitor · Recorded state

    redirected→Desconocido

    probe_inconclusive

  12. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  13. Availability monitor · Recorded state

    redirected→Desconocido

    probe_inconclusive

  14. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  15. Availability monitor · Recorded state

    redirected→Desconocido

    probe_inconclusive

  16. Availability monitor · Recorded state

    redirected→Desconocido

    stale_current_evidence

  17. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  18. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  19. Availability monitor · Recorded state

    redirected→Desconocido

    probe_inconclusive

  20. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  21. Availability monitor · Recorded state

    redirected→Desconocido

    probe_inconclusive

  22. Availability monitor · Recorded state

    Desconocido→redirected

    http_redirect

  23. Availability monitor · Recorded state

    Desconocido

    probe_inconclusive

  24. Availability monitor · First collection record

    Accesible

Proceso de respuesta ante amenazas Pipeline

Descubrimiento
Analysis
Notifications
Monitoring

14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Amenaza detectada
upservice-dienst.net detectados y puestos en cola para su análisis completo
05/09/2026
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
06/10/2026
URLScan.io Capture
Almacenado URLScan report with capture artifacts
05/09/2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in Wayback Machine — historical evidence archived
23/09/2026
VirusTotal
15/89 recorded on VirusTotal
13/09/2026
Detección de listas de bloqueo
Se encuentra en 2 blocklists: MetaMask, SEAL
16/10/2026
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
06/10/2026
CF Radar: Malicious
Cloudflare Radar classified this domain as phishing
Brand Impersonation
Impersonation of MetaMask
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
05/09/2026
Technical Analysis Recorded
El informe contiene tecnología almacenada o resultados de análisis forenses.
16/10/2026
Sent Report Recorded
Stored outgoing record associated with registrar Cloudflare, Inc., 1 abuse contact
abuse@omegatech.sc
05/09/2026
Lista de destrucción publicada
05/09/2026
Monitoring Continues
El dominio sigue siendo accesible o tiene acceso restringido; controles futuros pueden actualizar esta observación.
How we investigate & report

Public scans, evidence and abuse channels

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.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

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.

Related infrastructure

Shared hosting, registrar records and related domains

Dominios similares

79 dominios similares almacenados

Mostrar todo (67)
metasmask.io insertion Informe interno metramask.io insertion Informe interno mewtamask.io insertion Informe interno mmetamask.io homoglyph Informe interno mtamask.io omission Informe interno mwetamask.io insertion Informe interno nmetamask.io homoglyph Informe interno metamark.io bitsquatting Informe interno metamaskj.io addition Informe interno metammask.io homoglyph Informe interno metamnask.io homoglyph Informe interno emtamask.io transposition m-etamask.io hyphenation meamask.io omission meatmask.io transposition meramask.io replacement mertamask.io insertion metaamask.io repetition metaamsk.io transposition metaask.io omission metalmask.io insertion metamaask.io insertion metamadsk.io insertion metamaek.io replacement metamak.io omission metamas.io omission metamasak.io insertion metamasdk.io insertion metamask-io.com various metamasl.io replacement metamasm.io replacement metamsak.io transposition metamsk.io omission metamusk.io vowel-swap metamzsk.io replacement metarnask.io homoglyph metmaask.io transposition metmask.io omission metsamask.io insertion metsmask.io replacement mettamask.io repetition metwmask.io replacement metyamask.io insertion metzmask.io replacement meyamask.io replacement meytamask.io insertion mitamask.io vowel-swap mnetamask.io homoglyph mretamask.io insertion mrtamask.io replacement mstamask.io replacement mteamask.io transposition mwtamask.io replacement rnetamask.io homoglyph matamask.io bitsquatting mdtamask.io bitsquatting metamasi.io bitsquatting metamasj.io bitsquatting metamaska.io addition metamaskk.io addition metamaskl.io addition metamaso.io bitsquatting metamesk.io bitsquatting metamqsk.io bitsquatting metemask.io bitsquatting netamask.io homoglyph xn--metamas-bhb.io homoglyph

Evidence & investigation tools

Original reports, independent checks and evidence links

Datos y informes externos

Instantánea de evidencia enviada
Sent: Ledger records: 1 Case ID: PD-20260905-B14BB4 Recipient: abuse@omegatech.sc
PDF notice generated Notice text archived (613 chars)
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 (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.
Análisis en profundidad

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

¿Te ha afectado esta página web?

7 evidence signal groups linked 1 stored notification records Último activo conocido
If credentials were compromised, report immediately. Do not engage with recovery scammers.

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.

Official reporting routes
¡Cuidado con los estafadores que se hacen pasar por empresas de recuperación de datos! Los delincuentes pueden volver a contactar a las víctimas haciéndose pasar por investigadores, abogados o agentes de recuperación. No pague tarifas por adelantado ni comparta credenciales. Más información sobre el fraude en las ayudas de recuperación →
Informa a las autoridades locales

Seleccione su país para obtener contactos oficiales de cibercrimen o crear un borrador de queja →.

directorio de 97 países

Template-based draft · optional AI wording assistance requires separate consent

Borrador asistido por IA: el proveedor de IA procesa los detalles del incidente · Revíselo y envíelo usted mismo
After a phishing incident

Recomendaciones y consejos para las víctimas

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

¿Qué debo hacer ahora mismo?

Urgente

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Cambiar todas las contraseñas — correo electrónico, cuentas de Exchange, cualquier cosa que utilice la misma contraseña
  • Activar la autenticación de dos factores utilizando una aplicación de autenticación (no SMS). Desactivar la recuperación mediante SMS
  • Tarjetas de congelación si has introducido tus datos bancarios en la página de phishing

¿Qué información debo recopilar para mi informe?

Directrices del FBI

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Fechas y horas exactas — de cada transacción y del primer contacto con el estafador
  • Capturas de pantalla — páginas web fraudulentas, mensajes de chat, correos electrónicos, transacciones con monederos electrónicos, redes sociales
  • Todas las URL y dominios utilizados por el estafador (incluidos upservice-dienst.net)
  • Comunicaciones — correos electrónicos, mensajes de texto, números de teléfono y nombres de usuario que utilizó el estafador

Aunque no tengas todos los detalles — presenta la denuncia de todos modos. Incluso la información parcial sigue siendo útil para las investigaciones.

¿Dónde debo denunciar la estafa?

  • IC3 del FBI — Centro de Denuncias de Delitos en Internet (sistema federal de denuncia de EE. UU.)
  • Europol — Informes sobre la ciberdelincuencia en Europa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Policía local — deja constancia oficial, aunque no puedan actuar de inmediato

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Páginas web falsas — Clones idénticos al milímetro de sitios web legítimos, con dominios ligeramente modificados
  • Sacrificio de cerdos — Se ganaba la confianza de las víctimas a lo largo de varias semanas a través de Telegram, WhatsApp o aplicaciones de citas, y luego les robaban el dinero.
  • Estafas relacionadas con la recuperación — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Estafas basadas en la inteligencia artificial — los «deepfakes», el phishing automatizado y los sitios web generados por IA, que hacen que el fraude sea más difícil de detectar

¿Cómo puedo protegerme en el futuro?

  • Añadir a favoritos las páginas web oficiales — Nunca hagas clic en enlaces de correos electrónicos, mensajes directos o anuncios
  • Verificar dominios — comprobar si PhishDestroy antes de interactuar. Comprueba que sea HTTPS, la ortografía y la antigüedad del dominio
  • «Demasiado bueno para ser verdad» = estafa — rendimientos garantizados, recomendaciones de famosos, plazos urgentes

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Mantente informado, mantente a salvo

Supervisa las amenazas en tiempo real o impugna esta entrada si crees que se trata de un falso positivo.

Flujo de amenazas en tiempo real Reclamar este anuncio
Read the evidence in context

Acerca de este informe: upservice-dienst.net

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.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Incrustar este informe

Comparte esta información sobre amenazas en tu página web o blog

embed.html
<iframe
  src="https://phishdestroy.io/es/embed/domain/upservice-dienst.net"
  title="PhishDestroy threat report for upservice-dienst.net"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>