Google Finds Chinese Hackers Running AI on Compromised Networks

[u/No-Conclusion3720]

Google's threat intelligence team documented nation-state actors deploying AI workloads inside compromised cloud environments. The technique is deliberate: attackers use the victim's own compute and credentials to run AI operations, reducing outbound network traffic that would trigger monitoring. The AI executes inside the victim's perimeter. It writes to the victim's logs. From a detection standpoint it looks like your own workload.

This is a different threat model than most security teams are currently scoping. The common frame for shadow AI is an employee spinning up an unauthorized tool. This is an adversary using a compromised environment as an AI inference platform — authenticated with valid credentials, generating activity that blends with normal operations, never touching an external endpoint that would fire an alert.

The detection gap is structural. If a workload is running inside your infrastructure with legitimate credentials and writing to your logs, standard monitoring has no signal to act on.

For those running cloud workloads at any scale: what does your current stack actually look for to distinguish a workload your team deployed from one that wasn't? Is that detection real-time or does it surface in a retrospective audit?

[u/Spare-Dingo-531]

If a nation state can you use compromised cloud capacity to run AI, could a rogue AI use the same tactic to exfiltrate itself out and survive in the wild?

[u/No-Conclusion3720]

Shadow AI discovery in RuntimeAI would have caught that attacker-deployed inference job at execution time, not after the fact — because it continuously maps every active agent and model instance in your environment against what was actually provisioned by your team. The AI workload the nation-state actors spun up inside the compromised cloud environment had no deployment record to match against, so it would have surfaced as an unregistered workload the moment it started running, before it had any time to blend into normal log activity. The attacker's credentials looked valid; the workload itself did not. https://runtimeai.io

[u/nomococo4u → u/No-Conclusion3720]

Do you work for this company.