Kilowatto

Columns

The Blueprint for Disaster: When Technical Incompetence Exposes Citizens

2026-01-12 · By Esteban Rey (@Kilowatto)

There's a maxim in project management, both in engineering and public policy, that rarely fails: a bad idea with poor execution is the perfect recipe for disaster.

What we're experiencing in Mexico at the start of 2026 is not a random accident or an unpredictable surprise; it's the chronicle of a foretold catastrophe. Just a few months ago, under the banner of national security and the fight against extortion, a reform was approved that many of us warned would be toxic. I'm referring to the new Telecommunications and Broadcasting Law, published on July 16, 2025, which gave life to the new mandatory registry of mobile phone users.

The government's premise was seductive on paper but draconian in practice: building an exhaustive registry that would link our biological and legal identity to our phone line. However, many questions were left hanging in the air, tainted by political rhetoric: Who will protect this database that contains the metadata of our lives? How will it really be used? Who will have access? And the most disturbing of all: How can I, as a citizen, know who and how my data is being used?

Today, unfortunately, we have the answers. And they're terrifying.

Historical Stubbornness and Citizen Rejection

The idea of having a registry of phone users is not new in Mexico; it's a cyclical obsession of the State. We've already stumbled upon this stone in 2009 with the failed RENAUT of Felipe Calderón's administration, which ended with the database being sold on the black market in Tepito for pennies, and where, ironically, the president himself was registered with thousands of lines. We stumbled again in 2021 with the PANAUT, an even more aggressive attempt that required biometrics and was fortunately halted and declared unconstitutional by the Supreme Court in 2022.

The low participation of the population in this new attempt in 2026 is not apathy; it's an act of self-defense. It's a reflection of the rejection of intrusive surveillance of citizens' privacy. People intuit that giving their data to the State — or to concessionaires obliged by the State — doesn't guarantee security, but rather puts them in a showcase to be watched or, worse, commercialized.

The Execution of Telcel: "Vibe Coding" and Negligence

But if the legislative idea was already bad due to its invasive nature, the technical execution we saw this January was, to put it mildly, criminally negligent.

To "make the drink even more bitter," the implementation that Telcel — the dominant operator with over 80 million lines — deployed to generate this registry was an insult to the most basic cybersecurity practices. On January 9, 2026, the first day of the mandatory registration, its digital infrastructure collapsed not due to saturation, but due to incompetence.

I must confess something: since I wasn't personally affected by this law on my main line, I didn't pay much attention initially. However, I actively participate in several cybersecurity and technology forums — some populated by highly qualified people, ethical "White Hats," and others by enthusiasts with a lot of free time. What I saw in those spaces was alarming.

No NSA tools or Russian hackers were needed to exploit the system. With a bit of willingness and basic web development knowledge, anyone could exploit the vulnerability. What the journalistic reports and independent forensic analyses revealed was a software architecture made on the fly, what developers call "vibe coding": programming by intuition, without stress tests, without security audits, and hoping that "good vibes" will keep the server secure.

Anatomy of a Leak: The "Master Key" Exposed

The mistake was so elementary that it hurts to explain. The vulnerability resided in the eligibility API. When a user (or an attacker) entered a cell phone number in the web form to check if they should register, the server didn't respond with a simple "YES" or "NO."

Instead, the server ("Backend") returned a JSON object (a plain text format used for data exchange) that contained the complete client file.

Anyone who knew how to open their browser's developer console could see, in plain text:

This is not just a simple leak of a phone number. By exposing the RFC and CURP along with the name and phone number, Telcel handed over the "master key" for identity theft. With these data, a criminal can perform banking transactions, request credits in the victim's name, access government portals (like the SAT), or execute SIM Swapping attacks (line hijacking) with astonishing ease.

The most ironic and tragic thing is that this law was sold as a tool to prevent extortion. The result is diametrically opposite: now extortionists have a validated, updated, and free directory to make calls with "surgical precision," citing the victim's full name and tax data to sow terror.

Even after the scandal erupted on social media and independent media, the technical response was a cosmetic patch on the visual interface (Frontend), leaving the server's access points exposed for hours. It was sustained negligence.

The Tip of the Iceberg: Who Watches the Watchman?

This incident with Telcel should set off all the red alarms on the national dashboard. We can't see it as an isolated fact of a private company; it's the tip of the iceberg of a systemic problem in Mexico's digital infrastructure and its concessionaires.

If the largest and richest telecommunications operator in Latin America, with theoretically unlimited resources, couldn't protect a basic API on the first day of a legal mandate, what can we expect from projects directly managed by the government?

I'm referring to much more sensitive initiatives that are already underway or in planning:

The brutal lesson of the 2026 phone registry is that the State's regulatory capacity to demand data is inversely proportional to its technical capacity to protect it. We're building information repositories ("honeypots") that are irresistible to cybercrime, without having the necessary locks.

Who Watches the Watchman?

The fundamental question in a digital democracy is: Who watches the watchman and auditor?

Today, the answer seems to be "no one." Or worse, "we ourselves, when it's already too late." The autonomous bodies that should serve as a counterbalance, such as the INAI (now absorbed into functions by the Anticorruption Secretariat), face political challenges that dilute their ability to impose immediate sanctions on corporate or governmental giants.

The Telcel leak demonstrated that "digital civil death" — the threat of disconnecting those who don't register — is a coercion that puts citizens between a rock and a hard place: either you hand over your privacy to an insecure system, or you're left without communication.

As technologists, analysts, and citizens, we can't normalize incompetence. A bad idea (massive indiscriminate registration) executed with flaws (basic API vulnerabilities) is not "digital transformation," it's systemic negligence.

If we don't demand external, real, and public audits; if there are no devastating legal consequences for companies and officials that expose our data, then we're not living in an information society, but in an exposure society.

The 2026 registry has already failed in its promise of security. The only thing it has successfully achieved is demonstrating how fragile we are when the State decides to watch us without knowing how to care for us.