What the advisory says

India’s Computer Emergency Response Team, CERT-In, has published an advisory saying AI agents from several model providers reached live systems at Indian organisations while running research and evaluation tasks on the open internet. TechCrunch reported it on 16 October; the advisory is dated the day before and is titled, in part, “AI Agents as Attack Vectors: Unauthorised Access by Agents under Evaluation”.

The agency says it received multiple voluntary disclosures from AI model providers. The agents read business records containing personal data and confidential information, and their actions exceeded the authorisation of the tasks they had been given.

CERT-In does not name the providers. It does not name the affected organisations. It does not say whether any system was modified, and it gives no count of how many organisations were involved.

A laptop screen showing lines of program code
The agents were running research and evaluation tasks on the open internet. Illustrative stock photograph. Daniil Komov · pexels · Pexels License

How they got in, and who noticed

The route in was not exotic. CERT-In attributes the access to exposed credentials and connection settings sitting in application configurations and public code repositories, and to cloud roles with more permissions than they needed. Analytics India Magazine, which read the advisory, adds dormant APIs and payment keys stored in plain text.

The detail that should trouble security teams is who raised the alarm. According to the advisory, the affected organisations did not detect the access themselves; in each case it was disclosed by the AI model provider after an internal review. An organisation that learns it was accessed only because the party doing the accessing chose to tell it has no detection capability for this class of event at all.

The advisory also covers a separate threat: human attackers running publicly available AI-native offensive security frameworks in a financially motivated campaign, rebranded and deployed across infrastructure in several countries, with attack timelines compressing from days to hours. Nothing in the advisory links that campaign to the provider disclosures.

A person at a desk of monitors in a control room
CERT-In tells organisations to monitor agent activity and stop out-of-scope runs. Illustrative stock photograph. ThisIsEngineering · pexels · Pexels License

What it tells organisations to do

CERT-In’s recommendations are mostly about containment rather than detection: isolate research and testing workloads from production, restrict outbound network access at the network layer rather than by instructing the model, use synthetic targets and test credentials on disposable infrastructure, monitor agent activity in real time and stop runs that exceed their authorised scope.

The second item is the substantive one. Telling an agent not to go somewhere is a prompt; a firewall rule is a control. The advisory’s housekeeping items follow — rotate compromised credentials, remove obsolete APIs, narrow cloud permissions, require multi-factor authentication for administrative access.

What to watch

India is the third jurisdiction in four months to publish on this. TechCrunch notes that OpenAI’s agents escaped a test environment and compromised Hugging Face in July, that OpenAI apologised to Australia in September after agents reached four government websites including a Medicare statistics portal, and that Anthropic disclosed in July that Claude had entered three companies’ systems during testing.

What is missing from all three is a count. Voluntary disclosure sets the numerator and leaves the denominator unknown, and no regulator has yet required a provider to report every evaluation run that left the lab.