Ciberataque reportado contra el sistema administrativo de PDVSA con impacto operativo en disputa

What this source supports

• Kaspersky documented Lotus Wiper activity against Venezuelan energy and utility organizations
• the article explicitly states there is no proof Lotus Wiper was used in the PDVSA incident
• actor identity remains unknown

Evidence limits

Authoritative secondary coverage of Kaspersky research, but expressly not evidence that Lotus affected PDVSA.

Relevance to this case

Materially contradicts the inherited title/classification linking PDVSA to Lotus.

What this source supports

• Kaspersky documented Lotus Wiper against unspecified Venezuelan energy and utility organizations
• the reporting does not establish PDVSA as a Lotus victim

Evidence limits

The article identifies the sector/country campaign, not this PDVSA event.

Relevance to this case

Context only and insufficient for malware attribution to PDVSA.

What this source supports

• PDVSA publicly reported a cyberattack affecting its administrative system
• PDVSA attributed it to the United States without public technical evidence
• PDVSA said operational areas were unaffected

Evidence limits

Reports the company statement; does not independently validate cause, attacker or technical scope.

Relevance to this case

Same-day coverage of PDVSA’s official disclosure.

What this source supports

• PDVSA confirmed an administrative-system cyberattack and claimed operational continuity
• Reuters sources reported systems offline, manual work and suspended cargo deliveries
• no public evidence linked the event to the United States

Evidence limits

The operational-impact assertions are attributed to unnamed Reuters sources and conflict with PDVSA.

Relevance to this case

Directly documents the competing official and media accounts.

What this source supports

• PDVSA said only administrative systems were affected and operations continued
• Bloomberg/Reuters reporting described precautionary shutdowns and export disruption

Evidence limits

Derivative reporting; the extent and duration of operational disruption remain disputed.

Relevance to this case

Corroborates that conflicting impact accounts circulated.

What this source supports

• the article embeds an exact Con el Mazo Dando X post reproducing PDVSA's statement
• the embedded statement says administrative-system impact but no operational-area impact

Evidence limits

The outlet repeats the official narrative and does not independently establish attribution or technical cause.

Relevance to this case

Preserves the exact social-media reproduction of the PDVSA statement.

What this source supports

• the living roundup summarizes the official no-operational-impact claim and external reports of administrative/export disruption

Evidence limits

It is secondary synthesis, not ransomware proof; it neither establishes ransomware nor Lotus.

Relevance to this case

Context for the conflicting impact accounts only.

What this source supports

• PDVSA says it was the object of a cyberattack aimed at its operations
• PDVSA says it detected and neutralized the attempt
• PDVSA says impact was limited to its administrative system and operational areas/supply/export commitments continued
• PDVSA attributes the event to the United States

Evidence limits

Authoritative for what PDVSA reported, not independent proof of attacker, cause or complete impact.

Relevance to this case

Primary victim statement for event existence and official scope.

What this source supports

• the exact rendered post says PDVSA reported a cyberattack aimed at stopping operations
• its sole media item visibly reproduces the full PDVSA communiqué

Evidence limits

This is faithful publication of the official statement, not independent technical corroboration.

Relevance to this case

Exact social artifact embedded by an attached source.