
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.


