Near‑autonomous AI agents used in cyberattack on Taiwan government

What changed: Taiwan confirmed that suspected foreign hackers used a framework built on Hermes and OpenClaw agentic AI systems to mount a near‑autonomous intrusion against government networks, deploying up to eight sub‑agents per wave. Investigators say the agents mapped 21 systems, identified vulnerable APIs and an authentication flaw, installed backdoors, and ultimately exfiltrated roughly 1,395 files, 85 sets of credentials, and around 2,500 personnel records over four days.

Why it matters: This incident shows that off‑the‑shelf agent frameworks plus modest human direction can now automate much of a complex intrusion, collapsing the skill and time required for advanced attacks. Security and infrastructure teams need to assume attackers will use agents for reconnaissance, lateral movement, and exploit chaining, and design defenses that expect machine‑speed trial‑and‑error.

Try/watch: Prioritize hardening and monitoring of public APIs, SSO and identity services, and admin panels, and add detection rules for unusual automated browsing, credential testing, and tool‑like traffic patterns characteristic of agent frameworks such as Hermes‑style orchestrators.

Grok Bot points to always‑on AI coworkers that work across your apps

What changed: SpaceXAI and Cursor launched Grok Bot in early beta as a team of always‑on AI “teammates” that each run on their own virtual computer, sign into the same apps and websites humans use, and keep working on delegated projects after users close their laptops. The bots navigate software interfaces directly rather than relying on APIs, coordinate in group chats, and typically only request human approval for final outputs, with access currently limited to higher‑tier paid subscribers on desktop and mobile platforms.

Why it matters: This is a concrete step from chat assistants toward persistent digital coworkers that own end‑to‑end processes, which will force teams to redesign work around supervision, access control, and handoffs rather than ad‑hoc prompt sessions. For buyers and operators, the question shifts from “Can an agent do this task?” to “Which workflows are safe to hand over to an always‑running bot with login access to core systems?”.

Try/watch: Pilot always‑on agents only on low‑risk, well‑logged workflows (for example, data collection or internal reporting), define clear approval checkpoints, and ensure you can immediately revoke credentials and terminate the agent if behavior drifts.