Excluded / contextual

Outside the main registry and its statistics

Multi-incident summary

The ministerial statement named BCV within a national campaign involving multiple institutions without delimiting a BCV episode. Retain it as aggregate context; Banco de Venezuela is a different institution and its payment trouble is not assigned to BCV.

unconfirmed aggregate report Public report: Date confidence: Low

Mención del BCV en reportes agregados de ciberataques

El Banco Central de Venezuela fue mencionado en una declaración ministerial sobre instituciones presuntamente afectadas por ciberataques, reproducida el 14 y el 17 de agosto de 2024. Otras publicaciones del 12 y el 13 de agosto documentan la circulación anterior de esa narrativa agregada. Las cifras de modalidades, duración y volumen se refieren al conjunto nacional y no se asignan al BCV. No se delimitó un sistema, acción, fecha de actividad o efecto propio del BCV, ni continuidad con el reclamo distinto de White_Hunters del 13 de agosto. Esta referencia permanece excluida como contexto agregado no contable; ello no determina falsedad de la declaración.

Overview

Missing evidence

declaración o aviso directo del BCVpost exacto de un actor dirigido al BCV para este supuesto eventofecha y descripción de un incidente técnico individualtelemetría de DDoS, error 503 o medición de indisponibilidad del dominio BCVregistros o análisis forenseimpacto en sitio, sistemas, pagos, datos o usuarios

Impact details

Las fuentes sólo nombran al BCV dentro de listas agregadas. No documentan error 503, indisponibilidad, interrupción de pagos, acceso, filtración, sistemas, datos, personas o dinero afectados. El valor falso obligatorio de interrupción significa no establecido, no disponibilidad demostrada.

Classification & severity

Category
Undetermined
Subtype
unconfirmed aggregate report
Confidence
Low

Las fuentes incluyen al BCV en listas agregadas de organismos afectados, pero no describen un evento técnico individual ni vinculan al BCV con la estadística nacional de DDoS.

Severity assessment

Low
Public confidence
Limited

No se estableció un evento o impacto específico del BCV; la severidad sólo refleja una mención pública agregada contra una institución esencial.

Timeline

Publication

Radio Miraflores reprodujo una declaración que incluyó al BCV en una lista agregada de organismos afectados por ciberataques; no identificó un evento, técnica, actor o impacto específico del BCV.

Evidence & sources

6 sources
Primary Media report Source confidence: Medium

What this source supports

  • reports that minister Gabriela Jiménez named BCV among several organizations affected by cyberattacks
  • discusses service problems at Banco de Venezuela, a different bank, but does not report an analogous BCV outage
  • does not assign a specific technique, date, actor, technical artifact or impact to BCV

Evidence limits

Government-aligned media report reproducing a ministerial aggregate list; no direct ministry transcript, BCV statement, technical detail or independent target-specific validation was found.

Relevance to this case

Earliest recovered page naming BCV in the aggregate affected-organizations list; supports reporting provenance only.

Corroborating Media report Source confidence: Low

What this source supports

  • repeats a government-reported list of affected institutions that includes BCV
  • states that 65.52 percent of attacks in the national aggregate were DDoS
  • does not connect that aggregate percentage to BCV or provide a BCV-specific event, actor post, 503 observation, outage measurement or technical artifact

Evidence limits

Politically framed derivative reporting of aggregate government figures; target-specific technique, timing, actor and impact cannot be inferred.

Relevance to this case

Corroborates only that BCV appeared in the aggregate government list, not a discrete BCV incident.

Context Media report Source confidence: Low

What this source supports

  • an interview names BCV among several institutional/critical-infrastructure sites said to face cyberattacks
  • repeats aggregate modality percentages attributed to minister Gabriela Jiménez
  • does not establish that BCV itself suffered DDoS, downtime, compromise or impact

Evidence limits

Derivative interview/commentary that repeats aggregate official figures without a target-specific technical basis.

Relevance to this case

Weak later context for the aggregate list; it is not independent corroboration of a discrete BCV incident.

Context Media report Source confidence: Medium

What this source supports

  • Notitarde quotes Gabriela Jiménez saying attacks had affected 25 state institutions and specifically names the Bolsa de Valores de Caracas, Mincyt, BCV and SAIME among those attacked. She describes attacks lasting five to ten hours at an aggregate level.

Evidence limits

This is a government-reported aggregate claim reproduced by a news outlet, not a BCV incident report. It does not identify BCV system, exact incident time, method, technical data, or impact. The 30-million-per-minute number is a ministerial claim, not independently validated here.

Relevance to this case

Fresh, later report quoting the minister and explicitly naming BCV in the claimed group of affected institutions. Useful as official-claim provenance, not independent technical confirmation.

Context Media report Source confidence: Medium

What this source supports

  • Reproduces a list attributed to a ministerial presentation on August 12, including BCV, SAIME and CONATEL.

Evidence limits

Statement says 25 institutions but displayed list is broader; no per-target event/technique is mapped. This publication is earlier than the stored Radio Miraflores report.

Relevance to this case

earlier_aggregate_provenance

Context Media report Source confidence: Medium

What this source supports

  • Names Banco Central de Venezuela in a national ministerial allegation and describes creation of the cybersecurity council.

Evidence limits

BCV acronym appears as BVC but full entity name identifies BCV; target-specific event, exact timing and impact remain absent.

Relevance to this case

earlier_aggregate_provenance