# The Gentlemen claims an attack on DIRECTV Latin America

> The double-extortion group added the operator to its victim blog on November 17. The company has not confirmed the intrusion or its scope.
> By José Maldonado · Cybersecurity · 2026-11-19

A ransomware group added DIRECTV Latin America to its leak blog on November 17, 2026. That entry is the only reference to the incident: a claim no one has verified. The satellite television and internet operator has not confirmed the intrusion, has not discussed the scope, and no data theft or ransom has been reported. What has been published is the claim; everything else remains open.

The distinction between a claim and a verified fact is not a legal technicality. In double extortion, the group publishes the victim's name to pressure for payment, and that list mixes companies with demonstrated intrusions and organizations added without verifying anything. [DIRECTV Latin America's listing on the group's blog](https://noticias.dupin.com.ar/2026/11/the-gentlemen-reivindica-un-ciberataque-con-ransomware-contra-directv-latin-america) is documented; so are the company's silence and the gap between the two things.

The interest lies in the target, not the gang. DIRECTV Latin America operates in Argentina, Ecuador, Chile, Colombia, Uruguay, Peru, Barbados and Curaçao, a map that explains why an incident there would end up before several regulators at once and why confirmation, when it comes, will not be a single press release. Ransomware lists take days to clean up and the company may not yet know what to review: silence in the first hours proves nothing.

## What is established and what is not

A ransomware claim is read in three columns: what the attacker asserts, what the victim confirms and what a third party can verify. Today only the first has content.

Item

Status as of November 19, 2026

Publication on the group's blog

Established; entry dated November 17

Intrusion into the company's systems

Unconfirmed by the victim or by third parties

Data exfiltrated and volume

Unknown

Encryption of systems

Unknown

Ransom demand and deadline

Unknown

Countries or subsidiaries affected

Unknown

[The ransomware.live record](https://cyberthreatintelligence.net/ransomware-victim/directv-latin-america-thegentlemen-2026) places the organization in Argentina and assigns it 1,195 accumulated victims, a figure that measures the gang's activity and not the severity of this case. The record warns of something rushed coverage skips: the publication date is not the date of compromise. Some databases log the listing on the 16th; the report that spread the case came out on the 17th.

The Gentlemen operates with double extortion, like most gangs active since 2023. The order matters: first they exfiltrate, then they encrypt, and then they use the threat of publishing what was stolen as a second lever for payment. [The entry pattern analysts attribute to it](https://orbitaley.com/news/the-gentlemen-claims-ransomware-attack-on-directv-latin-america-yj2ct) points to poorly protected edge devices and remote access as the entry point. If they got in that way, the proof is in the operator's logs.

## Why an eight-country telecom is an easy target

An operator cannot go a week without billing. That dependence on continuity reduces its margin against extortion, and the volume of customers turns any exfiltration into a data protection problem with mandatory notification in several countries at once.

The other half of the problem is the surface. A telecom accumulates customer service, self-service portals, payment gateways and network diagnostics, and much of it runs on legacy software that no one updates because no one looks at it. The [1,094 flaws Microsoft closed in a single November](https://observatorioblockchain.com/en/cybersecurity/patch-tuesday-noviembre-2026-outlook-cero-dia/) give a measure of what accumulates when updates do not reach everything.

Technician access is the softest point. Broad permissions, shared passwords and remote administration consoles installed for an emergency that stay for five years. That door appears in almost every industry report and no new vulnerability is needed to walk through it.

If you administer a network with vendors who come in over VPN and a remote console on top of it all, the scenario sounds familiar. In November, [the 33 zero-days in N-able N-central](https://observatorioblockchain.com/en/cybersecurity/able2shell-n-central-33-cero-dias-nube-offline/) took down the vendor's cloud and forced managed devices to be switched off locally: whoever attacks the technician's tool gets into every network that technician administers.

For a gang that publishes unverified names, the calculation comes out favorable even when the attack does not succeed: the mention costs nothing and no one audits its list. The economics of ransom work the same way. Every day without service translates into claims, customer credits and technicians dispatched, a cost that usually exceeds what the gang demands, and the decision to pay is made with a calculator.

## How a claim of this kind is verified

The first place to look is the company itself: press release, notice on the corporate website, email to customers. A 48-hour silence proves nothing, but a statement changes the status of the entire table above.

The second filter is independent technical signals: data for sale on another forum, samples published by the gang, verifiable screenshots. When a group shows no evidence for days, the probability of a bluff rises. Formal attribution, when it exists, is signed by an organization with a name and a document, such as [the FBI linking the Binance theft to a North Korean group](https://observatorioblockchain.com/en/cybersecurity/fbi-robo-binance-corea-del-norte/); an extortion blog is not that.

The third filter is regulators, and here rushed coverage usually gets it wrong. [Argentina's data protection law](https://www.recordinglaw.com/es/world-laws/world-data-privacy-laws/argentina-data-privacy-laws/) does not require notifying a breach to the Agency for Access to Public Information: Resolution 47/2018 recommends it and non-compliance counts as evidence in a case file, but it sets no deadline. For banks the clock exists: [Central Bank Communication A 8280](https://www.bcra.gob.ar/Pdfs/comytexord/A8280.pdf) requires notice within the first hour, and the public sector reports to CERT.ar within 48 hours under Disposition 7/2021. No deadline by itself obliges a telecom, and that is the part the reports usually omit.

## What does not change even if the attack is confirmed

If the intrusion is confirmed tomorrow, the response will not differ from what any playbook has recommended since 2021: isolate, restore from verified backups, review remote access and write off what has already left. What is done wrong is almost always the same.

Backup is the first point. A restoration plan that has never been tested is not a plan, it is a folder, and with the data volume of an operator a full restoration takes no less than a week.

The second is the inventory of remote access, which in environments with vendors and external technicians is usually larger than the security team believes. No one knows how many accounts are still alive until they all have to be closed at once.

The third is communication, and there the cost is not measured in engineering hours. A telecom that takes five days to say something loses the narrative and its corporate clients, who are the ones who read the fine print of the contract. [When Microsoft 365 went down and its status page went with it](https://observatorioblockchain.com/en/technology/caida-microsoft-365-status/), the detail was discussed more than the outage. The first statement sets the version that is remembered.

## The difference between a blog and a breach

The DIRECTV Latin America case is a reminder of method: an entry on a leak blog is a self-interested assertion, not a fact, and treating it as such does the work of whoever is extorting. The press bears the tension between novelty and verification.

When there is confirmation, the story will be a different one and will be told with data. In the meantime, what is verifiable is the calendar: on November 17 a name appeared on a list, and the rest is still waiting for someone with access to publish it.
