Interrupción de BNC APP y BNCNET con presunto compromiso atribuido a Qilin

What this source supports

• BNC says a technological platform disruption prevented BNC APP and BNCNET operation
• debit-card POS transactions remained available
• ATMs, 216 agencies and the 24-hour hotline remained available
• BNC says accounts/information were safeguarded and technicians were restoring service
• does not state cyberattack, ransomware, breach, cause or exact start/end time

Evidence limits

The document is hosted by Banca y Negocios rather than an evident BNC-owned domain, has no visible date or signature and could be replaced. It does not identify the cause as malicious.

Relevance to this case

Strongest source for BNC acknowledgement and channel scope, with explicit provenance/date limitations.

What this source supports

• reports failures from approximately 21:00 on 1 July affecting BNC APP/BNCNET
• reports BNC partial restoration around midday 2 July with intermittent access attributed by the bank to high demand
• reports debit/POS unaffected and ATMs/telephone channels available
• quotes the x01x00 taunt but explicitly says its version could not be verified

Evidence limits

The article confirms the outage and BNC response but does not technically establish its cause. It expressly treats the x01x00 claim as unverifiable.

Relevance to this case

Best complete contemporaneous narrative joining the outage, official response and claim while preserving uncertainty.

What this source supports

• caption reports BNC APP/BNCNET interruption and partial restoration
• reproduces BNC statement that debit operations remained active
• calls x01x00 unverified and attributes Qilin/USD 8 million to anonymous VenariX sources
• states BNC did not confirm ransomware

Evidence limits

Social-media reproduction and reporting, not a forensic investigation; the ransomware attribution remains explicitly unconfirmed.

Relevance to this case

Contemporaneous visible preservation of the outage and BNC communiqué with careful qualification of the actor claim.

What this source supports

• exact text addresses @bncbanco_ and asks whether everything is okay
• includes misspelled hashtag #Ramsonware and Good Luck
• does not name Qilin, state responsibility, describe access, demand money or show evidence

Evidence limits

A targeted taunt is not a clear admission and does not establish Qilin identity, malicious causation or compromise.

Relevance to this case

Primary provenance for the x01x00 message mentioned by contemporaneous media.

What this source supports

• says anonymous sources claim Qilin may have compromised BNC
• claims a demand of up to USD 8 million
• quotes an earlier VenariX post that only described a possible incident based on user reports
• provides no artifact, named source, actor statement or technical evidence

Evidence limits

Anonymous-source monitoring claim. It supports provenance of the Qilin/USD 8 million allegation, not its truth.

Relevance to this case

Direct public origin located for the attribution repeated by later media.

What this source supports

• article concerns the April 2026 BNC listing claim
• retrospectively repeats a July 2025 Qilin/USD 8 million narrative
• later paragraph attributes the 2025 claim to VenariX rather than a victim or actor statement

Evidence limits

Published nine months later for the April 2026 publication and not independent confirmation of the 2025 attribution. The relationship between the 2025 and 2026 publications remains unresolved; neither separate intrusions nor dataset identity is established.

Relevance to this case

Retained only as retrospective context and provenance trail; not primary proof of the July 2025 cause.

What this source supports

• Reports customer access failures on 30 June and the bank's generic platform-incidence notice.

Evidence limits

Reported local failure time is not forensic attack onset; generic wording also appears in later bank notices.

Relevance to this case

Bound the observed service interruption and continuity; does not establish cyber cause.

What this source supports

• Reports the same interruption continuing beyond 24 hours and alternatives remaining available.

Evidence limits

Not independent evidence of malicious causation.

Relevance to this case

Bound the observed service interruption and continuity; does not establish cyber cause.

What this source supports

• Reports restoration of the continuing online-service disruption after roughly 48 hours.

Evidence limits

Restoration is continuity evidence, not a new incident or proof of ransomware.

Relevance to this case

Bound the observed service interruption and continuity; does not establish cyber cause.