Skip to main content
Mallory
← Back to News
leaked-secret-api-keyai-platform-securitycloud-misconfigurationbuild-pipeline-compromise

Hosted AI Models Face Abuse Risks as Credentials Leak Through Public Code

Breach & Incident Intelligence · 2 sources · Updated 3mo ago · First seen Sep 3, 2026

Hosted AI Models Face Abuse Risks as Credentials Leak Through Public Code

Permiso documented how hosted AI models can be hijacked for “dark roleplaying,” underscoring that externally accessible model services can be manipulated for harmful or policy-evading use cases. The issue adds an abuse-management requirement to AI deployments alongside conventional application and cloud security controls.

Separately, Wiz found hundreds of validated, still-active secrets in public code repositories during a month-long scan, with AI-service credentials disproportionately represented. Jupyter notebooks and AI-agent configuration files such as mcp.json frequently exposed keys through hardcoded values, outputs, diagnostics, and error messages; 56% of company-impacting secrets were in employees’ personal repositories. Organizations should expand secret scanning to AI providers, scan Git history and CI/CD pipelines, block commits containing notebook outputs, and revoke or rotate exposed credentials.

Is this vendor in your chain?See attribution, scope, and your downstream exposure.
Check the blast radius
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

2 events
  1. Reported Jun 17, 20251y ago

    Microsoft rates disclosed exposed secret as Critical

    The researchers reported that a secret they disclosed to the Microsoft Security Response Center was rated Critical and could have enabled exposure of sensitive HR data.

    AI Secret Leaks in Public Code Repos: Warning to Developers | Wiz Blog
  2. Reported Jun 17, 20251y ago

    Researchers identify active AI-service secrets in public repositories

    A month-long scan of thousands of public code repositories found hundreds of validated exposed secrets, many still active. AI-service credentials represented three of the five most common validated secret types, and Jupyter Notebook files were the most leak-prone file type.

    AI Secret Leaks in Public Code Repos: Warning to Developers | Wiz Blog
Do you run this?See attribution, scope, and whether this vendor sits anywhere in your supply chain.
Get the Full Incident Picture
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.