{"id":3108,"date":"2026-03-13T16:53:10","date_gmt":"2026-03-13T19:53:10","guid":{"rendered":"https:\/\/wai.global\/?p=3108"},"modified":"2026-03-13T16:53:13","modified_gmt":"2026-03-13T19:53:13","slug":"el-vibecoding-llego-al-estado-y-los-atacantes-lo-saben","status":"publish","type":"post","link":"https:\/\/wai.global\/en\/el-vibecoding-llego-al-estado-y-los-atacantes-lo-saben\/","title":{"rendered":"Vibecoding has come to the State. And the attackers know it."},"content":{"rendered":"

For years, the biggest threat to the security of a public system was the easy password. The classic \u201c123456\u201d on the administrator account. Also the shared access between ten people or the session that nobody closed.<\/p>\n\n\n\n

But according to Google's Cloud Threat Horizons Report H1 2026, that is changing. The report, which looks at the second half of 2025, shows that the most commonly used attack vector was no longer credential theft, but the exploitation of vulnerabilities in the software installed by users.<\/strong> 44.5% of intrusions started there. Weak passwords, which until the first half of the same year accounted for 47.1% of initial accesses, fell to 27.2%. A complete turnaround in less than twelve months.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Why this matters especially in the public sector<\/h2>\n\n\n\n

Government agencies are not the most obvious target for a cyberattack. They don't have cryptocurrencies or handle credit cards. But they do have something that is worth a lot: citizen data, access to critical infrastructure<\/strong> and, in many cases, systems developed or adapted internally with little technical oversight.<\/strong><\/p>\n\n\n\n

This is where vibecoding comes in.<\/p>\n\n\n\n

The term, popularized in the last two years, describes a way of developing software where the programmer does not write code line by line: he asks an AI (Artificial Intelligence) tool to do it and approves what appears on his screen. The result is functional and often quite good. But with a particularity: who approves it does not always understand what they are approving.<\/strong><\/p>\n\n\n\n

In the private sector, this is already generating debate. In the public sector, where technical teams are smaller, budgets are tighter and the pressure to digitize is higher than ever, the phenomenon is amplified. Municipalities that previously could not afford their own development can now have an application ready in hours. This is a real advance. But it is also software that no one reviewed and with vulnerabilities that no one knows about... until a cybercriminal exploits them.<\/strong><\/p>\n\n\n\n

<\/p>\n\n\n\n

The time that no longer exists<\/h2>\n\n\n\n

The most worrying data in Google's report is not the percentage of attacks but their speed.<\/p>\n\n\n\n

In the past, when a vulnerability was released, organizations had weeks to apply the patch. That window allowed IT\/Systems teams to plan, test and update without rushing. In 2025 that window collapsed. Attackers went from public disclosure to active exploitation in a matter of days. In some cases documented by Google, they deployed cryptocurrency miners in less than 48 hours from the announcement of the flaw.<\/p>\n\n\n\n

For any public agency that depends on the goodwill of small teams, no budget, no audit, no technical training or a system developed with IA without a formal review process, that margin of days does not exist in practice and the patch arrives when it arrives, when something has already happened.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

The credentials did not disappear: they were added<\/h2>\n\n\n\n

It would be a mistake to read this report as \u201cpasswords no longer matter\u201d. What the data shows is an accumulation of problems, not a replacement.<\/p>\n\n\n\n

83% of the compromises in cloud environments analyzed involved at some point credential theft, phishing or abuse of SaaS service tokens. Attackers walk through a door and look for keys inside. Y 73% of the incidents were aimed at data theft.<\/strong><\/p>\n\n\n\n

In a public agency that translates into: municipal registry, employee files, files in process, contracts, medical records, medical records<\/strong> if there is an integrated health system. Information that has no obvious market price, but that can be used for extortion, for espionage or simply to paralyze the operation of a government.<\/strong><\/p>\n\n\n\n

<\/p>\n\n\n\n

What this means for decision makers<\/h2>\n\n\n\n

The instinctive response is usually technical: \u201csystems need to be upgraded\u201d, \u201cpersonnel need to be trained\u201d. This is necessary, but not sufficient.<\/p>\n\n\n\n

The underlying problem is one of technological governance (who decides what software is installed in a municipality, who allows the implementation of software developed with AI without adequate supervision, what process exists to apply patches when a vulnerability appears, or who has real visibility over access).<\/p>\n\n\n\n

Vibecoding is not the enemy. It is a tool. The problem is adopting it without the controls that any serious development process requires:<\/strong> code review, dependency management, access auditing, incident response protocols.<\/p>\n\n\n\n

In the public sector, these controls do not always exist because no one demanded them. And because, until now, attacks came through the weak password door, which is easier to understand and easier to communicate.<\/p>\n\n\n\n

The new attack surface is more technical, faster and harder to see. But the consequences for management are the same: systems down, data compromised, citizens affected and officials answering questions no one wants to answer.<\/strong><\/p>\n\n\n\n

What can be controlled<\/h2>\n\n\n\n

Not all the news is bad. The same Google report documents that improvements in identity controls and secure default settings pushed attackers into more sophisticated vectors. In other words: when one door closes, attackers look for another. That's not a failure; it's evidence that the controls work.<\/p>\n\n\n\n

For public agencies that are in the process of digitization, there are concrete decisions that reduce exposure:<\/strong><\/p>\n\n\n\n

    \n
  • Require software vendors to have a permanent updating process and response times in case of vulnerabilities. It is not enough for the system to work: it must be maintainable.<\/li>\n\n\n\n
  • Separate systems according to their criticality. When the systems are internal, it is not necessary for everything to be on the same network or with the same level of access. A shift system does not need to have the same perimeter as the records system or the payroll system.<\/li>\n\n\n\n
  • Implement multifactor authentication for administrative access. This is the most cost-effective control available and is still lacking in most public agencies in the region.<\/li>\n\n\n\n
  • Have a protocol, however basic, for when something goes wrong. Know who calls whom, what gets disconnected first, and how the incident is communicated to the public.<\/li>\n<\/ul>\n\n\n\n

    The digital transformation of the State does not stop because new risks appear. But it does require that decision-makers understand that to digitize without considering security is to build on shaky ground.<\/strong><\/p>\n\n\n\n

    Vibecoding is not a problem, but its misuse is the cause of an undesirable effect; however, good technological governance is the key to secure systems, vibecoded or not.<\/p>\n\n\n\n

    Data source: Google Cloud Threat Horizons Report H1 2026.<\/em><\/p>","protected":false},"excerpt":{"rendered":"

    Durante a\u00f1os, la mayor amenaza para la seguridad de un sistema p\u00fablico fue la contrase\u00f1a f\u00e1cil. El cl\u00e1sico “123456” en la cuenta del administrador. Tambi\u00e9n el acceso compartido entre diez personas o la sesi\u00f3n que nadie cerr\u00f3. Pero seg\u00fan el Cloud Threat Horizons Report H1 2026 de Google, eso esta cambiando. El informe, que analiza […]<\/p>\n","protected":false},"author":3,"featured_media":3113,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[31],"tags":[37,38,45,50],"class_list":["post-3108","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ciberseguridad","tag-ciberseguridad-en-el-estado","tag-ciberseguridad-en-los-gobiernos","tag-inteligencia-artificial","tag-vibecoding"],"_links":{"self":[{"href":"https:\/\/wai.global\/en\/wp-json\/wp\/v2\/posts\/3108","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wai.global\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wai.global\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wai.global\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/wai.global\/en\/wp-json\/wp\/v2\/comments?post=3108"}],"version-history":[{"count":1,"href":"https:\/\/wai.global\/en\/wp-json\/wp\/v2\/posts\/3108\/revisions"}],"predecessor-version":[{"id":3114,"href":"https:\/\/wai.global\/en\/wp-json\/wp\/v2\/posts\/3108\/revisions\/3114"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wai.global\/en\/wp-json\/wp\/v2\/media\/3113"}],"wp:attachment":[{"href":"https:\/\/wai.global\/en\/wp-json\/wp\/v2\/media?parent=3108"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wai.global\/en\/wp-json\/wp\/v2\/categories?post=3108"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wai.global\/en\/wp-json\/wp\/v2\/tags?post=3108"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}