Interfaz en español. Las fichas, los resúmenes y las fuentes conservan su idioma original.
Mercado Bitcoin confirms security incident; deposits and withdrawals suspended
Análisis del incidente
Mercado Bitcoin confirms a security incident and a temporary suspension of deposits and withdrawals. The provider says customers suffered no losses and no data leaked; those statements have not been independently established.
Quiénes deben revisar: Mercado Bitcoin customers, treasury and operations teams, and organizations with transfers or workflows dependent on the platform.
Check the official service status before scheduling transfers, reconcile pending movements and track MB’s investigation and reopening notices.
¿Qué ocurrió y por qué es relevante?
On November 2, Mercado Bitcoin said it had identified and contained a security incident in one of its systems during the early morning. It temporarily suspended deposits and withdrawals as a precaution while investigating, tracing assets and coordinating with authorities.
MB states that customers suffered no losses and that no data leaked. These are the provider’s statements; the two notices do not supply an independent assessment or a complete technical account of the incident.
A second statement says work continues to restore operations safely and publishes destination addresses on EVM, Bitcoin, Solana, Stellar and TRON for identification and asset tracing. Publishing those addresses does not establish the amount lost, funds recovered or completion of restoration. The reviewed update does not announce that deposits or withdrawals have reopened.
The reviewed official statements disclose no loss amount. This advisory therefore does not characterize a US$40 million theft as confirmed. Root cause, entry method, attacker attribution and an independently verified customer-impact assessment remain unresolved.
For customers and organizations using MB, the immediate operational check is service availability and the state of pending transfers. Preserve transaction records, reconcile requests before retrying them and follow official status updates. No customer-side CVE, software patch or AI involvement is established by these statements.
- Proveedor / autor
- Mercado Bitcoin
- Divulgado
- 2 nov 2026
- Última revisión de evidencia
- 2 nov 2026 UTC
¿Qué evidencia respalda este aviso?
Evidencia del incidente
Fundamento de la prioridad
The provider confirms an incident and a precautionary service suspension. Review operational dependencies this week; customers with pending transfers should check status now. No customer-side software flaw or patch is identified.
¿Qué implica para los entornos de IA?
The reviewed statements do not establish AI involvement. Teams using automated transfer workflows should verify service availability and reconcile pending requests before resuming them.
Fuentes de este aviso
- Mercado Bitcoin official statement: security incident and precautionary suspensionMercado Bitcoin · Revisado 2 nov 2026 UTC
- Mercado Bitcoin update: restoration work and destination addresses for asset tracingMercado Bitcoin · Revisado 2 nov 2026 UTC
Historial editorial1 entrada
Added Mercado Bitcoin’s two November 2 statements, the temporary suspension and operational checks. Customer-impact assurances remain attributed to MB; no loss amount or completed restoration is established.
Prepará tu respuesta
Usá esta lista para evaluar si el aviso afecta a tus sistemas, registrar las acciones de tu equipo y compartir el resultado. Radar no escanea ni verifica tu entorno.
Los cambios se guardan automáticamente en este navegador. No se sincronizan con tu equipo ni se envían a Oktsec.
1. Evaluá si aplica a tu entorno
Leé el aviso y sus fuentes; después registrá tu decisión. Si tenés dudas, elegí «Requiere verificación».
2. Registrá la respuesta
Indicá el sistema y la persona o equipo responsable. Actualizá cada acción y agregá una referencia al ticket o notas sobre lo revisado.
Verify service availability through official channels
Check Mercado Bitcoin’s current notices before initiating or scheduling deposits or withdrawals. The reviewed update describes restoration work, not completed reopening. Record the time and scope of any later service-status confirmation.
Agregar evidencia o notas
Usá solo referencias. No guardes credenciales ni datos confidenciales acá.Reconcile pending transfers and operational dependencies
Record pending requests, transaction identifiers, timestamps and account statements. Review workflows that depend on MB availability, including automated retries. Confirm each pending request’s state before retrying it to avoid duplicate instructions.
Agregar evidencia o notas
Usá solo referencias. No guardes credenciales ni datos confidenciales acá.Use the official address list for investigation
If you handle blockchain monitoring, compare relevant transaction records with the destination addresses published in MB’s second statement, retaining the network and source. MB published them for identification and tracing; a match alone does not establish attribution, total loss or customer impact.
Agregar evidencia o notas
Usá solo referencias. No guardes credenciales ni datos confidenciales acá.Track confirmed findings and verify support requests
Keep the provider’s statements about customer losses and data separate from independently verified findings. Follow official updates on scope, cause and reopening. Verify unexpected recovery or support messages through established channels; never share private keys or seed phrases.
Agregar evidencia o notas
Usá solo referencias. No guardes credenciales ni datos confidenciales acá.
3. Compartí el plan
Descargá un archivo Markdown con tu decisión, los estados de las acciones, las notas y las fuentes. Compartilo con tu equipo o adjuntalo a un ticket.
Sistemas afectados y correcciones
Compará la versión en ejecución y la configuración con las indicaciones del proveedor.
| Producto | Afectado | Versión corregida / acción |
|---|
Confirmá con el proveedor las correcciones adaptadas a tu distribución. Coincidir en el producto no basta para establecer exposición.
Evidencia y fuentes
Por qué tiene esta prioridad
The provider confirms an incident and a precautionary service suspension. Review operational dependencies this week; customers with pending transfers should check status now. No customer-side software flaw or patch is identified.
Criterios de prioridadFuentes
Los datos técnicos provienen de estas fuentes. Las prioridades y las acciones recomendadas son el análisis de Oktsec.
- Mercado Bitcoin official statement: security incident and precautionary suspensionMercado Bitcoin · Aviso del proveedor · Revisado 2 nov 2026 UTC
- Mercado Bitcoin update: restoration work and destination addresses for asset tracingMercado Bitcoin · Aviso del proveedor · Revisado 2 nov 2026 UTC
Registro técnicoProductos, identificadores y detalles de respaldo
| Producto / servicio | Mercado Bitcoin deposits and withdrawalsMercado Bitcoin |
|---|---|
| Evidencia | Incidente confirmado por el proveedor |
| Exposure | Depende de la aplicación o configuración |
- Divulgado
- 2 nov 2026
- Registro revisado
- 2 nov 2026 UTC
Para entornos con agentes de IA
The reviewed statements do not establish AI involvement. Teams using automated transfer workflows should verify service availability and reconcile pending requests before resuming them.