
An AI Tool Hit the Commission's HR Systems. Your Low-Priority Fixes Just Got Urgent
On Thursday the European Commission confirmed that a cyberattack on its internal systems was carried out with a publicly available AI tool. The systems hit were Sysper, the HR platform where Commission staff check payslips, request leave and log their hours, and the system for medical reimbursements. Some of these services were down for more than ten days.
For a company of 200 or 2,000 people, the useful part of this story is how this kind of tool works, and what that does to the list of "minor" security findings that almost every IT team keeps and rarely finishes.
What the Commission has said, and what it hasn't
The intrusion was detected on 22 October and confirmed as a cyberattack on 26 October, according to Infosecurity Magazine's account of the 19 November press briefing. Spokesperson Thomas Regnier said several applications were taken down as a precaution and most have been restored, that there was no ransomware demand, and that the investigation has found no evidence of a data breach "affecting Commission staff as a whole". The European Data Protection Supervisor and CERT-EU, the cybersecurity service for EU bodies, have been informed.
Euronews reported that Sysper was working again on Thursday while the staff health insurance system was still unavailable, and named the tool as ARTEX. The key open question, it notes, is whether the attacker reached the data in those HR systems: names, pay grades, home addresses and contact details of officials.
So the facts are limited. We don't know the entry point, the attacker, or whether data left the building. What we do know is a lot about the tool, because two official bodies have published on it this month.
What ARTEX actually does
CERT-EU's 5 November warning describes ARTEX as an open-source, LLM-driven penetration-testing platform. An operator writes a goal in plain language, the system breaks it into steps, and agents run reconnaissance and testing with real tools. It has no model of its own; it plugs into whichever language model the operator chooses. CERT-EU says it saw similar AI-driven activity against EU institutions and that this "highly likely" involved ARTEX.
The sentence in that post that matters most for ordinary companies is about scale. ARTEX, CERT-EU writes, can test large numbers of low-complexity misconfigurations, "including those a human tester would notice but not have time to check", and it can work through long attack chains without getting tired.
The FBI's FLASH alert of 13 November adds numbers. Malicious actors have used ARTEX since at least August 2026, across sectors from finance and manufacturing to healthcare and legal services. Some intrusions went from first targeting to privileged access in under three hours. The original developer pulled the GitHub repository in October, but forks, archived copies and a commercial version keep it available, and researchers counted more than 1,600 publicly exposed ARTEX consoles in early November.
The FBI also lists the kind of systems the tool is good at finding: partner and supplier portals, mobile backends, employee applications, sales-support systems, legacy services, third-party integrations, and "applications created across different business units". In the Commission case, CSO Online reports that ARTEX appeared to be used mainly to search for and locate credentials.
The low-priority list is now the attack path
Every IT team has a backlog of findings marked low or medium. An old test environment still reachable from the internet. An admin panel that should sit behind a VPN. A storage key in a configuration file that nobody rotated after the contractor left. Each one on its own looks like a weekend job for later, and for years that judgement was reasonable, because an attacker needed time and skill to find them and chain them together.
CERT-EU's advice ends with a line that quietly reverses that judgement: retain all findings, including non-severe ones, in the remediation cycle, to prevent AI-enabled tooling from chaining minor misconfigurations into higher-impact attack paths.
My reading is that this is the real news for a mid-size company. Nobody is going to aim an expensive human team at a furniture maker in Gabrovo. An automated tool that walks through thousands of targets in parallel doesn't need to choose. It only needs one forgotten key and one admin page that answers from the internet. The economics that used to protect smaller companies, being not worth the effort, get weaker when the effort is close to zero.
Where AI projects add side doors
There is an uncomfortable connection to the work many companies are doing right now. Each AI pilot, automation flow or connector tends to bring its own access: an API key for a language model, a service account that reads the shared drive, a token that lets a workflow tool write to the CRM, a small web app the sales team asked an agency to build. These are exactly the "third-party integrations" and "applications created across different business units" in the FBI list. They are usually set up quickly, by someone outside IT, and they rarely have an owner after the pilot ends.
CERT-EU's continuous measures include ensuring that security monitoring "also covers AI tools and internet-connected assets that use AI processes". The FBI, in the data it asks victims to share, includes unusual token consumption and API billing anomalies. Read together, the message is simple: an AI tool your company uses is an asset like any other, and its keys can be found like any other.
Hypothetical example. A 250-person distributor runs a quotation assistant that a marketing agency built last spring. It sits on a cloud subdomain, uses a language-model API key stored in an environment file, and reads the price list from a shared folder through a service account with full read access to the drive. The pilot worked, people use it, and nobody in IT has it on their list. None of these details is critical on its own. Chained together, they are the kind of path CERT-EU is describing.
What to do with this next week
You don't need an incident to learn from this one. The most useful single step is an inventory of the side doors, with a named owner for each, and the AI tools on the same list as everything else. Concretely, that means one table with these columns: what the system is, who built it, who owns it now, whether it is reachable from the internet, what keys or accounts it uses, how much access those keys have, and when they were last rotated.
Two of the expert comments in the coverage are worth adding to that exercise. Brian Levine of Control Risks, quoted by CSO Online, suggests giving every token and service principal only the access it needs, "so a found key opens a closet, not the vault". Noah Kenney of Digital 520 points out that when the Commission took HR systems down, work moved to spreadsheets, email and manual approvals, which usually have weaker controls. His advice is to define a secure fallback process before an attack rather than improvise one during it.
If AI tools in your company have spread faster than anyone's ability to say who owns them, that is a governance problem before it is a security one. A register of AI systems with owners and access rules is the same list your security team needs, and it is cheaper to build before someone else maps it for you.
What we still don't know
The Commission's investigation is ongoing, and some of what is reported today may change. The FBI and CERT-EU material describes the tool in general, not the specific path into Sysper. It would be wrong to read this case as proof that AI tools are the cause of every new breach. The narrower point holds regardless: the cost of finding small mistakes has dropped, so small mistakes deserve a place on the list and an owner who closes them.


