Microsoft says it has observed threat actors using an agentic offensive framework to search public GitHub repositories for exposed credentials, application secrets and AI service keys, then use the results in follow-on cloud attacks. In one observed case, an AI agent moved from searching for a client secret to exfiltrating data from Azure Key Vault within five minutes.

The company’s researchers linked the activity to valid application credentials used against Microsoft Entra ID, Azure and Microsoft 365 resources. They also described request sequences in which failed cloud API calls were quickly retried with corrected methods or versions, behaviour that Microsoft assessed as adaptive troubleshooting by the tooling. The reporting does not show that every exposed secret led to compromise, but it demonstrates how automation can compress reconnaissance, validation and exploitation.

The practical lesson is that deleting a secret from a repository does not neutralise it. Organisations must rotate exposed credentials, review service-principal sign-ins and activity logs, and assume that public secrets may already have been collected. Managed identities, short-lived credentials and least-privilege access reduce the usefulness of material that does escape.

Microsoft’s observations are vendor threat intelligence, not an independent census of attacks. Even so, the detailed indicators and mitigation steps make the disclosure operationally useful.


Execution Level Governance- What audit-ready agent governance actually looks like
David Girvin, founder and CEO of Assury argues that model-in-the-loop review, AI governing AI, is fundamentally unreliable for regulated environments: even the best-performing models miss a meaningful share of violations, the reviewing model is typically provided by the same vendor being reviewed, and prompt injection or context poisoning can compromise both the acting agent and its supposed overseer simultaneously. He makes the case for deterministic, architecturally enforced controls instead, walking through Assury's approach of autonomy zones, session risk accumulation, and credential starvation, which lets a compromised agent be cut off from its tools instantly rather than relying on time-boxed access. The conversation touches on why David is sceptical of just-in-time credentialing as a solution for agent security more broadly, since agent sessions don't run on predictable human timescales, along with the current gap between how identity and security vendors are pitching agent protection and what he sees happening at the execution layer in practice. He also discusses the compliance and audit implications of probabilistic decision-making, arguing that regulated industries will increasingly need tamper-evident, hash-chained audit trails that can withstand scrutiny from auditors and regulators who are only beginning to understand agentic risk, and reflects on a named frontier lab's own published framework as an example of the gap between research and practitioner reality. Elsewhere, David reflects candidly on building a bootstrapped security company in an increasingly crowded market, why he turned down aggressive VC funding to stay in control of the product, and what a credible third-party assessment of his own gateway would need to look like given that Assury sits directly in the execution path for every customer's agents.
Share this post
The link has been copied!