Research reportsGoogle Threat Intelligence Group

Google threat research observes AI workflow abuse, highlighting protection of development credentials and cloud resources

Google's threat intelligence team published new observations on AI abuse, covering agent workflows, the open-source supply chain and unauthorised use of cloud AI resources. The findings reflect the team's available sample and highlight the need to monitor AI accounts, API credentials and usage together.

Original illustration of an administrator organising an account inventory and security keys
Illustration · Source ↗ · About this image ↗

Source Facts

On 8 September, Google's threat intelligence team released AI Threat Tracker, summarising its observations from Q2 2026. The report describes some activity moving from general question answering towards agent workflows and automation, and examines supply chain risks in developer tools and open-source dependencies.

The report also discusses stolen model, application and API credentials and unauthorised use of cloud computing resources. These conclusions draw on Google's incident response, tracking and platform defence data. They describe a research sample, not complete statistics for every business environment or incident worldwide.

Next Steps for Businesses / Editorial Observations

Treat AI services as business assets that need management: inventory accounts, keys and usage first. Review sources before adding development dependencies; an AI recommendation is no reason to skip checks.

Next steps you can take

  • Inventory AI platform accounts and API credentials, recording owners, purposes and permissions. Disable unused entries.
  • Set alerts for unusual sign-ins and usage. When adopting AI development tools, review third-party packages and the origins of connected tools.

Original sources

GTIG AI Threat Tracker: From Prompting to Autonomy – The Evolution of Adversarial AI

Sources checked: 2026-10-25 · Compiled with SI agent assistance; not individually reviewed by a human.

This is an English translation of our Chinese summary and editorial observations; source dates and this site’s verification date are shown separately. If an original advisory changes, refer to the source.

Back to news ←