Hugging Face, the widely used platform for sharing open-source machine learning models and datasets, has disclosed a security breach it says was carried out by an autonomous AI agent system. How the attack unfolded In a blog post published Thursday (July 16), the company said that earlier that week, it identified unauthorized access to some internal datasets and to several credentials used by its

Hugging Face, a prominent platform for open-source machine learning models and datasets, has confirmed a security breach that it attributes to an autonomous AI agent system. The company disclosed the incident in a blog post published on Thursday, July 16, following the detection of unauthorized access earlier that week.
The intrusion began with a malicious dataset that exploited two code-execution vulnerabilities within Hugging Face's dataset processing pipeline. Specifically, a remote-code dataset loader and a template-injection flaw in a dataset configuration were leveraged to execute code on a processing worker. This initial access allowed the attacker to escalate privileges to node-level access, subsequently harvesting cloud and cluster credentials. Over a weekend, the attacker moved laterally into several internal clusters.
Hugging Face's investigation is ongoing, but as of their disclosure, there is no evidence that the attacker accessed partner or customer data, nor is there any indication of tampering with public, user-facing models, datasets, or Spaces. The company also verified that its software supply chain, including container images and published packages, remained uncompromised.
In response to the breach, Hugging Face has taken several remediation steps. They have blocked the dataset code-execution paths that were exploited, ejected the attacker from affected clusters, and rebuilt all compromised nodes. Additionally, the company is in the process of revoking and rotating all compromised credentials and tokens. New security measures include implementing additional guardrails and stricter admission controls on their clusters, alongside enhancements to their detection and alerting systems to ensure high-severity signals are routed to responders within minutes. As a precautionary measure, Hugging Face has urged its users to rotate their access tokens and review recent activity on their accounts.
The New York-based company detailed its use of AI to detect and analyze the attack. An anomaly-detection pipeline, which employs LLM-based triage over security telemetry, correlated various signals to flag the compromise. Subsequently, the attacker's action log, comprising over 17,000 recorded events, was fed into LLM-driven analysis agents. These agents were instrumental in constructing a timeline of the attack, identifying affected credentials, and pinpointing indicators of compromise, which have not been publicly shared. The analysis also helped map decoy activity engaged in by the attacker.
Based on the forensic analysis, Hugging Face concluded that the attack was executed by an autonomous agent framework utilizing an unspecified large language model (LLM). This framework reportedly executed thousands of individual actions across a swarm of short-lived sandboxes and employed a self-migrating command-and-control infrastructure staged on public services.
While Hugging Face successfully leveraged LLMs for analysis and response, they noted challenges with commercial API-based frontier models. These models' guardrails often blocked defender requests containing real attack commands, exploit payloads, and command-and-control artifacts. Consequently, the company performed its forensic analysis using GLM 5.2, an open-weight model, on its own infrastructure. Hugging Face advises other organizations to prepare similar self-hosted setups for future incident investigations to maintain privacy of attacker data and credentials.

JetBrains is urging Cadence users to revoke and rotate all credentials following a security incident last month in which unidentified threat actors exploited a recently disclosed critical vulnerability in TeamCity to breach its own environment. "Cadence users should immediately revoke or rotate all credentials and secrets that may have been used to run their Cadence executions," JetBrains said.
A weakness has been identified in Tenda CP3 27.5.57.101. This issue affects some unknown processing of the file Net/NetCheckPing.cpp. This manipulation of the argument interface_name/host causes os command injection. The attack can be initiated remotely.
A security flaw has been discovered in Tenda CP3 27.5.57.101. This vulnerability affects the function SystemAsh of the file Apis/system.c of the component Kylin. The manipulation of the argument AlarmVoiceURL results in os command injection. It is possible to launch the attack remotely.

OpenAI has announced a $1 billion commitment to provide subsidized access to its Daybreak AI cybersecurity tools for under-resourced critical infrastructure defenders. The initiative, named Daybreak for Frontline Defenders, will offer AI models, training, and technical support over the next six months, prioritizing water and wastewater utilities, electric grid operators, and local government entities. This move aims to equip organizations with limited budgets and staff against increasingly sophisticated cyber threats.

Attackers are exploiting a new unpatched vulnerability in Magento Open Source and Adobe Commerce that lets them run malicious code on an online store's server without logging in, Dutch e-commerce security company Sansec said in an advisory published on September 5. Sansec, which discovered the flaw and named it StyleSmuggler, said attacks started on September 4. "Sansec is publishing early
In BPF instructions that load/store a value from/to a scratch memory register the register index is an unsigned 32-bit integer and must not exceed 15, but libpcap BPF interpreter does not validate the value. In particular uncommon use cases a crafted filter program can cause the interpreter to try reading and writing the OS process memory in the 16GiB starting at the current stack frame on 64-bit architectures and in the entire address space on 32-bit architectures.