Search the evidence

Find the signal.

Search titles, impact clusters, countries, organizations and the full text of every analysis.

2 stories found

Jade light passes through stained-glass doorways toward an hourglass and a defensive gate that stops some signals.
SecurityGlobal+1 clusters01

AI attacks are getting faster. Can defenses keep up?

The uncomfortable question is not whether an AI agent looks like a skilled hacker. It is whether defenders can recognize and interrupt an intrusion before the next consequential step. The FBI's November 13 ARTEX advisory describes criminal use of an LLM-driven penetration-testing framework and reports some intrusions progressing from initial targeting to privileged access in under three hours. That is a reported example, not the average time for every attack. The advisory consolidates a threat already described in earlier vendor reporting, including Microsoft's November 6 financial-sector analysis. It is not the discovery of an entirely new form of crime, and its citations are not independent replications of every underlying case. The important change is the possible compression of the response window when criminals combine automation with familiar access weaknesses. For a security team, that shifts the practical test from owning a monitoring tool to completing a response. Who can revoke a compromised credential? Which supplier-facing systems have an owner? Can someone contain a suspicious nonhuman identity without waiting for several departments to agree? These are organizational questions with technical consequences. The evidence also resists fatalism: the FBI account includes defensive controls blocking attempted lateral movement. AI assistance does not make an intrusion unstoppable. Our reading is that reducing exposed access, restricting privileges and rehearsing containment may matter more when attackers can move faster. More alerts alone are not the same thing as more time to act.

3 min
Ink illustration of defenders limiting red paths into a bank vault.
SecuritySoutheast Asia / Global+2 clusters02

AI joins the bank break-in. The weak spots look familiar.

A bank customer should not have to know what an AI agent is to expect their account information to be protected. That is the human stake behind Microsoft's latest threat report. The company says a financially motivated group it tracks as Storm-3358 began using ARTEX against financial organizations in October, alongside conventional automated tools. The reported weaknesses include exposed systems and stolen credentials—not a mysterious new law of computing. That makes the story more practical, not less serious. If software can pursue several stages of an intrusion with less manual intervention, an ordinary mistake can have a shorter useful life for defenders. Our inference is that response readiness matters alongside prevention: who can revoke access, isolate a system and establish what happened? Microsoft's account does not supply a sector-wide victim count, quantified losses or a controlled measurement of AI's added contribution. Those omissions should remain visible. A separate AWS reference design, found in the morning radar, offers a constructive comparison. It describes isolated coding tasks and a human decision before merging changes. It also says its input screening does not cover everything the agent subsequently reads. That is not a fix for the reported bank campaign; it is an example of stating a control's boundary honestly. For organizations considering agents, the useful question is not whether the software sounds trustworthy. It is whether the surrounding system limits what a compromised or mistaken process can do. Better tools deserve attention. Unrestricted authority is a different purchase, and customers should not unknowingly pay for it.

3 min