Fallas de pago de Farmatodo con presunto hackeo de sus sistemas

What this source supports

• Sumarium says it directly observed Farmatodo accepting only cash on the morning of 27 June and external POS card processing in the afternoon
• it says mobile payment, delivery-card payment and prepaid mobile reloads were unavailable all day
• it links the exact x01x00 status asking Farmatodo whether everything was okay
• it labels the event a hack and links the account to Medusa/Digitel without technical proof or a responsibility claim

Evidence limits

Strongest public evidence for the service contingency because the outlet states it observed the payment methods. Its conclusions about hacking, Medusa and prior incidents are not accompanied by technical evidence, victim confirmation or a responsibility claim.

Relevance to this case

Original report underlying close derivatives; supports the outage and contingency details, not cyber cause or attribution.

What this source supports

• the article reports cash-only operation on the morning of 27 June and external POS card processing later that day
• it reports mobile payment, delivery-card payment, self-checkout and prepaid reload unavailability
• its embedded Tecnochui post reports delivery, self-checkout and integrated POS failures and says attribution is only possible
• the article calls the event a hack and says Medusa ransomware was used without supplying technical or victim evidence

Evidence limits

Contemporaneous secondary reporting consistent with the original Sumarium account. It does not identify its own store observations, technical evidence or an official Farmatodo source; its ransomware/Medusa wording is unsupported.

Relevance to this case

Corroborates the payment-channel contingency and preserves the Tecnochui report, but does not independently establish cyber cause or attribution.

What this source supports

• the report says multiple users and news outlets reported delivery, self-checkout and integrated POS failures
• it explicitly says Farmatodo had issued no official report
• it presents Tecnochui’s attribution as possible and says other users believed the same possibility
• it reports the x01x00 question to Farmatodo but does not provide evidence that the account caused the outage

Evidence limits

The article is based on social-media reports, contains no direct Farmatodo or technical evidence and moves from explicit possibility to a group label without substantiation. It corroborates reports of disruption, not a hack or actor.

Relevance to this case

A contemporaneous Venezuelan report that preserves absence of an official statement and the speculative nature of attribution.

What this source supports

• at 22:30 integrated POS and self-checkout remained unavailable
• the post reports no integrated-card, Biopago, Zelle or mobile-payment-change service and no connection between online shopper and the online payment gateway
• portable POS remained available
• the author said no Farmatodo statement addressed whether sensitive information might be at risk

Evidence limits

A named contemporaneous observer, not an official Farmatodo statement or forensic source. The post supports channel status and fallback availability, not cause, compromise, actor or data exposure.

Relevance to this case

Adds detailed late-evening availability and contingency status independent of the Medusa inference.

What this source supports

• the post reports delivery, self-checkout and integrated POS services down
• it describes the actor inference only as possibly the same criminal associated with Banco de Venezuela and Digitel
• its sole image is a screenshot of the separate x01x00 question to Farmatodo

Evidence limits

Contemporaneous social report. Its service-status statement is useful corroboration, while its attribution is expressly speculative and relies on a separate ambiguous post.

Relevance to this case

Preserves the exact social report embedded by both stored articles and separates outage reporting from attribution speculation.

What this source supports

• the exact post addresses @Farmatodo and asks Is everything okay?
• the post existed before later public outage reports on 27 June
• the post contains no responsibility claim, Medusa name, ransomware reference, technical detail, demand, proof or media

Evidence limits

An ambiguous target-directed question. Timing and prior media associations can motivate investigation but cannot establish responsibility, ransomware, access or causation.

Relevance to this case

Primary provenance for the exact post that articles treated as an actor signal; retained chiefly to show why it is inadequate attribution evidence.

What this source supports

• Preserves Sumarium's alleged payment-system hack and reported cash/external-POS observations for June 27.

Evidence limits

Fresh readable reproduction; original Sumarium was ordinary 403 in this pass. Attribution to Medusa/account remains inference rather than evidence.

Relevance to this case

accessible_publisher_reproduction