Presunta extorsión de Qilin contra BNC con amenaza de divulgar datos

What this source supports

• HookPhish recorded bnc.com.ve under Qilin with discovery on 7 April 2026
• the page labels the item ransomware/data breach

Evidence limits

Feed-derived page with no actor artifact, technical evidence, sample or independent validation; its categorical attack/data-breach wording is not established.

Relevance to this case

Corroborates circulation and approximate claim date only.

What this source supports

• CriptoNoticias reported the April Qilin/BNC claim based on FalconFeeds
• the article expressly states that BNC had not confirmed or denied the alleged attack
• it distinguishes the prior July 2025 BNC/Qilin episode

Evidence limits

Independent newsroom publication, but the incident claim is derivative of FalconFeeds and no technical or victim evidence is supplied.

Relevance to this case

Strongest independent report for the public claim and explicit lack of confirmation, not proof of compromise or impact.

What this source supports

• DeXpose reported that Qilin publicly named BNC on 7 April
• the report says the actor threatened to release data unless negotiations began

Evidence limits

Secondary CTI/feed report with no original actor statement, sample, telemetry or independent breach validation.

Relevance to this case

Supports report existence and threat-to-publish wording only.

What this source supports

• FalconFeeds publicly reported BNC as a purported Qilin victim
• the attached Qilin-style card names WWW.BNC.COM.VE, shows 7 April 2026 and says 13 photos

Evidence limits

The tracker itself uses “reportedly.” The card documents a listing representation but does not authenticate the actor portal, any sample, intrusion, ransomware execution or impact.

Relevance to this case

Best visible provenance for the April public listing claim.

What this source supports

• VenariX said BNC may have suffered another Qilin attack
• its embedded claim cites anonymous sources and an alleged 8-million-dollar demand
• its image shows a Qilin-style BNC listing with 13 photos and pixelated lower thumbnails

Evidence limits

Uses conditional language and anonymous sourcing. The alleged 8-million-dollar amount is also associated with the July 2025 report and is not independently established for April 2026. The relationship between the 2025 and 2026 publications remains unresolved; neither separate intrusions nor dataset identity is established.

Relevance to this case

Corroborates contemporaneous circulation of the listing claim only.

What this source supports

• VenariX characterized an attached BNC platform-incident notice as vague confirmation
• the notice itself says only that BNC was restoring a platform incident and does not mention ransomware or Qilin

Evidence limits

The notice wording is independently reported as BNC’s 20 March 2026 availability incident and contains no April date or ransomware acknowledgement. It cannot confirm the 7-April Qilin claim.

Relevance to this case

Mis-correlated context and approval-only source-detachment candidate; preserved pending user approval.

What this source supports

No supported claims are recorded for this source.

Evidence limits

Account, body, date and media are unavailable; the URL slug alone is not evidence.

Relevance to this case

Approval-only source-detachment candidate; retained only as explicit unavailable provenance pending user approval.

What this source supports

• the post documents partial restoration after the outage reported in July 2025
• the caption explicitly says BNC had not confirmed ransomware

Evidence limits

This source concerns July 2025, not the April 2026 listing claim. The relationship between the 2025 and 2026 publications remains unresolved; neither separate intrusions nor dataset identity is established.

Relevance to this case

Mis-scoped duplicate source attachment and approval-only detachment candidate; preserved pending user approval.

What this source supports

• Public monitor lists www.bnc.com.ve under Qilin.
• Discovery timestamp is 7 April 2026 22:46 UTC; estimated attack date is 7 April.

Evidence limits

Estimated attack-date methodology is not supplied; equals discovery day and cannot be treated as proved intrusion date. Leak screenshot, stolen data and external credential links were not opened. Historical child access only; subsequent exact-entry security block preserved. No future browser/HTTP/reader/protocol request permitted.

Relevance to this case

Preserve precise public monitor discovery timestamp and limits of estimated attack date; investigate continuity.

What this source supports

• Lists BNC domain and Qilin with 7 April discovery/attack-date fields.
• Explicitly labels status claimed.

Evidence limits

85 confidence is the publisher's score, not registry confidence or forensic proof. No basis establishes activity date or distinct 2026 access.

Relevance to this case

Preserve another public claimed-status listing and date/methodology limits; no assumed independent corroboration.

What this source supports

• Reports generic BNC platform-incidence/restoration notice on 20 March.
• Freshly viewed notice matches the wording/design of VenariX's April attached notice.

Evidence limits

Visual matching only, no byte/hash identity comparison. Wording alone cannot establish a common underlying cyberattack.

Relevance to this case

Document March notice provenance and visual match; prevent April availability notice from becoming attack confirmation.

What this source supports

• Displays victim bnc.com.ve, Qilin, April8 Date Discovered and unknown leak size.

Evidence limits

Header says data breach, but supplies no incident narrative, original artifact, access time or validation. April8 discovery differs from April7 monitoring elsewhere and proves neither a new event nor an error. Root also read the current safe public metadata body. A separate generic credential-exposure section explicitly disclaims necessary connection to the ransomware item; its aggregate counts are not adopted as effects or new incidents. No personal entries, links or credential samples inspected.

Relevance to this case

Document the monitor's explicit Date Discovered semantics and unknown leak size; not an independent corroboration or initial-access date.