Interrupción del Banco de Venezuela atribuida a un presunto ciberataque

What this source supports

• The general platform failure began late on 15 September and suspended branch, card, mobile-payment, transfer, foreign-exchange, Biopago and balance-query services
• the bank publicly said it was working to restore its platform and closed offices on 16 September
• the report predates the 17 September cyberattack allegation and independently establishes outage timing and scope

Evidence limits

Strong contemporaneous outage reporting. It does not establish the cause or distinguish malicious activity from internal failure.

Relevance to this case

Added as the strongest independent source for start date, affected services and pre-allegation outage.

What this source supports

• The official bank account said it was working to restore the platform within hours
• the bank said its offices would not provide commercial service on 16 September
• the post does not allege or establish a cyberattack

Evidence limits

First-party operational notice; it establishes acknowledgment and restoration work, not technical cause.

Relevance to this case

Added as exact browser-verified official outage evidence predating the attack allegation.

What this source supports

• The platform had been unavailable for more than 100 hours and users could not access funds or banking services
• the bank announced electronic services would become available on 20 September at 14:00
• the article preserves both the official attack claim and an unattributed internal-obsolescence alternative; neither is forensic proof

Evidence limits

Independent reporting supports duration and customer impact. The 16-million figure and internal-failure explanation are source claims, not verified measurements or forensics.

Relevance to this case

Added as independent impact and restoration-timeline evidence.

What this source supports

• The Venezuelan government publicly alleged sabotage, a terrorist attack and a massive hack against the bank platform
• the official statement said users could not perform normal operations and that gradual restoration had begun
• EFE published no forensic evidence independently confirming attack cause, data alteration or attribution

Evidence limits

Wire report reproducing an official allegation. It is authoritative for what the government said, not independent technical validation.

Relevance to this case

Retained for the 17 September official allegation and reported user impact; attack causation remains explicitly unverified.

What this source supports

• PRIMICIA reproduced the Venezuelan economic vice-presidency communiqué alleging a massive hack and intended data alteration
• the communiqué said the source had been detected and neutralized and services were being restored gradually
• neither the page nor the communiqué publishes forensic evidence, technical indicators or an identified actor

Evidence limits

Contemporaneous local reporting of a visible official communiqué. The statement asserts attack and data-alteration intent but supplies no independently verifiable technical evidence.

Relevance to this case

Retained as the clearest visible copy of the official allegation and restoration statement, with confidence reduced from high to medium.

What this source supports

• The official Banco de Venezuela account acknowledged ongoing restoration of channels and financial services on 17 September
• the attached government communiqué alleged a terrorist attack and massive hack and promised account/data integrity
• the visible post and attachment establish the official position and restoration activity, not forensic confirmation of cause or data alteration

Evidence limits

High-confidence first-party evidence for acknowledgment, restoration work and the official allegation. It does not independently prove the alleged attack, actor, vector or data impact.

Relevance to this case

Retained as browser-verified primary evidence for the bank statement and restoration phase, not as technical proof of attack causation.

What this source supports

• The official bank card said the platform and systems had been fully restored and electronic channels would begin becoming available at 14:00 on 20 September
• the card repeated the bank cyberattack narrative and asserted data/fund integrity
• the post is primary for restoration timing and official position, not forensic validation

Evidence limits

First-party restoration statement. Its attack and integrity assertions are not independently verified.

Relevance to this case

Added as exact browser-verified primary evidence for the end of the principal outage.

What this source supports

• The bank warned that some transactions might not be visible immediately and that in-transit movements would be processed progressively
• users reported balance and transaction-display discrepancies
• these reports do not establish permanent data alteration, loss, exfiltration or attack causation

Evidence limits

The exact page is currently blocked by Cloudflare. A matching same-day report preserves the bank warning and user complaints, but neither source proves data corruption.

Relevance to this case

Retained as impact evidence for delayed transaction visibility, with corrected date and explicit accessibility limitation.

What this source supports

• Users reported Banco de Venezuela availability problems on 1 October
• the article says the bank had suffered a seven-day instability period after the September outage
• the 1 October symptoms coincided with the scheduled monetary-reconversion interruption and cannot establish uninterrupted incident duration

Evidence limits

User-report synthesis during the scheduled reconversion window. It supports later complaints, not technical cause or continuous duration from the September incident.

Relevance to this case

Retained as later context and user-impact evidence; no longer used to prove a continuous cyberattack through 1 October.

What this source supports

• The government replaced the Banco de Venezuela president days after the outage
• the article reports Delcy Rodríguez later alleged U.S. origin and cited 14 million affected customers
• the management change and later attribution are contextual and do not independently establish cause

Evidence limits

Later contextual reporting. The official U.S.-origin claim has no published forensic support, and the personnel change does not establish causation.

Relevance to this case

Retained as management and attribution context only; purpose corrected from corroborating.

What this source supports

• Bloomberg Línea reported the Banco de Venezuela platform was down from 15 through 20 September and affected transfers, cards and access for a reported 14 million users
• the article presents the official U.S.-origin allegation alongside infrastructure and reconversion explanations
• no forensic evidence independently validates any cause

Evidence limits

Strong secondary timeline/context source, but it relays competing explanations and does not provide attack telemetry.

Relevance to this case

Added to preserve the five-day outage boundary and causal uncertainty.