The European Commission's HR systems were breached by attackers using ARTEX, an open source penetration testing framework. The notable part isn't the tool's sophistication. It's how little skill the tool needs to find the keys to an organization's cloud.
Commission officials detected the intrusion on October 22 and cut off much of the access to affected systems for more than 10 days. Several applications have since been restored. Spokesperson Thomas Regnier said, "As a protective and preventive measure, we temporarily took down several applications and most of them have since then been restored," and added, "We have not detected any evidence of a data breach affecting Commission staff as a whole."
Regnier said the European Data Protection Supervisor was informed of the attack, "so there was no hiding whatsoever." He declined to go into detail while the investigation continues, but he confirmed that "it is a campaign, so there was a series of incidents." Commission officials say they're now checking other systems preventively and staying in close contact with CERT-EU and the EDPS.
A key hunter, not a password cracker
The FBI flagged ARTEX on November 13, describing it as an autonomous penetration testing framework that attackers are adopting fast. The FBI advisory says malicious actors have used it since at least August 2026 against organizations in financial services, government, technology, defense, semiconductor, energy, healthcare, manufacturing, telecommunications, and legal sectors.
The speed claim is the one to watch. According to the advisory, ARTEX "significantly reduces the time required to chain attack techniques, with some intrusions progressing from initial targeting to privileged access in under three hours." It also lets people with minimal technical expertise run multi-target operations at once.
ARTEX does far more than credential discovery, but in the Commission attack it seems to have been used mainly to find and locate credentials. The FBI says it can "automatically map effective permissions of Azure credentials–SAS tokens, Service Principals, Kudu credentials, Storage Account keys–using sub-second capability checks." That's the core of the threat: the tool doesn't break authentication. It checks what you've already left lying around and tells the attacker what each key can open.
ARTEX has been on security operations teams' radar since GitHub released it in July. Widespread misuse led GitHub to make it unavailable on October 8. That didn't end the problem. The FBI says "ARTEX remains widely accessible through independent routes and mirrors on code-sharing platforms."
Why the keys are the problem
Brian Levine, a partner at consulting firm Control Risks, argues that this tactic doesn't look like what most security teams are built to catch. There's no malware dropper or zero-day to fingerprint.
"ARTEX doesn't need to steal your keys. It finds the ones you left lying around, like a SAS token in a code repo, a storage key in a config file, or a Kudu credential nobody rotated. Then it tries each one against every door in under a second," he said. "Picture a burglar walking the block at 3 a.m. and checking every car door handle. He isn't breaking glass. He's taking inventory of what you left unlocked and AI lets him work a thousand blocks at once."
That analogy captures why defenders struggle. Each exposed secret looks like a minor hygiene issue on its own. Combined with automated checking at scale, those small gaps become a map of entry points.
The fallback is where it gets messy
Noah Kenney, principal consultant at Digital 520, was unimpressed with how the Commission described the incident. "The Commission says it has no evidence of a breach affecting its staff 'as a whole,' which is very different from saying that there is no evidence of a breach affecting any of the staff," Kenney said. "The wording doesn't give me much comfort."
His sharper point concerns the response itself. Taking HR systems offline is disruptive, and that disruption creates its own exposure. "When payroll, leave, and medical reimbursement systems go down, people start using spreadsheets, email and manual approvals," he said. "Those workarounds often have weaker access controls and worse audit trails than the systems taken offline." His advice is blunt: "Enterprises need to define a secure fallback process before the attack, because improvising one often leads to greater exposure."
Why HR is the target
Levine said choosing HR as a target makes sense from an attacker's perspective. "HR systems are a prize. Names, home addresses, pay grades and health insurance records for EU civil servants make a ready-made targeting list for espionage and social engineering," he said. "Whether or not data left the building, every Commission employee should prepare to receive a very convincing phishing email soon."
That's the part that outlasts the incident. Even if no bulk data left the network, the records themselves are useful for crafting convincing lures. Expect staff to be targeted with pretexts that reference real pay, leave, and benefits details.
Levine's advice for CISOs is specific: "Get secrets out of code and pipelines and rotate anything that has been exposed. Give every token and service principal only the access it needs, so a found key opens a closet, not the vault. Put cloud admin interfaces behind private access."
If your organization runs Azure workloads, the practical first step is a sweep of repositories, pipeline configs, and storage settings for SAS tokens, service principal secrets, and Kudu credentials. Start there, before the next access log tells you the same story.