Loading story…
An IBM Consulting expert demonstrated how employees sharing production source code with public AI tools can inadvertently expose proprietary algorithms and sensitive business logic. When such code is submitted to generative AI platforms, the information may be incorporated into the model's training data, potentially allowing similar code or formulas to be revealed to other users in the future. This risk is exacerbated by insufficient employee awareness, weak governance, and the absence of robust AI usage policies, making it critical for organizations to implement clear guidelines, approved tool lists, and targeted training to prevent inadvertent data leaks.
Separately, SAS Institute, a major analytics and AI software provider, experienced a breach in which threat actors claimed to have stolen source code and documentation. While the compromised files were reportedly outdated, dating from 2003 to 2011, the exposure of source code—even if old—remains a significant risk, as attackers may use such information to develop exploits or target customers. These incidents underscore the persistent threat posed by both inadvertent and malicious source code leaks, highlighting the need for comprehensive data protection strategies and vigilant monitoring of both employee behavior and external threats.
Track how attackers are adapting to this technology.
2 events from the most recent confirmed update back to the earliest known activity.
Help Net Security published coverage warning that a quick AI-related check could expose a company's secrets, framing the issue as an intellectual property and data leakage risk. The reference provided does not describe a specific incident, victim, or remediation event.
A reported breach involving SAS Institute surfaced, with claims that outdated information had been stolen. The available reference does not provide further details on the timing, scope, or affected individuals.
Follow how adversaries are adapting to this technology, and where it touches your stack today.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
The widespread adoption of generative AI (GenAI) tools in software development has significantly increased productivity, enabling developers to document, write, and optimize code at unprecedented speeds. According to a 2023 McKinsey study, organizations have rapidly integrated AI into their development workflows, with 83% using AI for code creation and 57% relying on AI-powered coding tools as a standard practice. However, this surge in AI-assisted coding has introduced new security risks, as traditional security models focused on perimeter or infrastructure controls do not adequately protect the data and code generated by these tools. Studies have revealed that nearly half of code snippets produced by popular AI models contain vulnerabilities, underscoring the prevalence of insecure code generation. High-profile incidents, such as Samsung's 2023 ban on ChatGPT following a sensitive code leak, highlight the real-world consequences of insufficient safeguards when using GenAI in development environments. The responsibility for securing data and code remains with developers, even as cloud providers secure the underlying infrastructure. The rapid pace of AI-generated code has outstripped the ability of traditional secure coding training to keep up, shifting the focus from training human programmers to ensuring that AI systems themselves are capable of secure coding. Industry experts note that AI is currently less effective at producing secure code than human programmers, with multiple studies and reports from sources like Schneier on Security, Veracode, and SC Media confirming this trend. The volume of vulnerabilities continues to rise, with over 47,000 publicly known vulnerabilities expected in a single year and at least 130 new vulnerabilities reported daily. This ongoing wave of vulnerabilities leads to constant exploitation and patching, further emphasizing the need for secure coding practices at the AI level. While AI has delivered substantial productivity gains—developers report 30% to 40% increases—these benefits are undermined by the security shortcomings of AI-generated code. The industry is now at a crossroads, where the imperative is to teach AI systems to code securely, rather than relying solely on human oversight or post-development security reviews. Integrating security into the AI coding process and providing developers with tools that embed data protection are seen as essential steps to address these emerging challenges. The shift towards AI-driven development necessitates a reevaluation of security strategies, focusing on proactive measures that align with the realities of modern software engineering. Without such changes, organizations risk exposing themselves to significant security threats stemming from the very tools designed to enhance their productivity.
Jun 29, 2026
Organizations are facing escalating security exposure from employee and developer use of public AI services without adequate controls. A viral social-media trend prompting ChatGPT to “create a caricature of me and my job based on everything you know about me” is being cited as a visible indicator of **shadow AI** and potential **data leakage**, because users may be sharing work context and sensitive details into non-sanctioned LLM accounts and then posting outputs publicly. The public sharing can also aid **social engineering** by revealing roles, access, and other targeting cues; if an attacker compromises an employee’s LLM account, they may be able to review prompt history for sensitive information. Separately, Cyble Research and Intelligence Labs (CRIL) reported widespread **credential mismanagement** involving OpenAI/ChatGPT API keys, identifying **5,000+ public GitHub repositories** with hardcoded credentials and roughly **3,000 production websites** exposing active keys in client-side assets (e.g., JavaScript). CRIL noted that secrets often persist in commit histories, forks, and archived projects, and that automated scanning/indexing can shrink the time from exposure to abuse to minutes—enabling unauthorized API usage, cost fraud, and potential downstream compromise where those keys are tied into broader application workflows.
Jun 29, 2026
Artificial intelligence is rapidly transforming the cyber threat landscape, introducing new risks and amplifying existing ones. Recent research revealed that 65% of top AI firms have leaked verified secrets such as API keys and credentials on GitHub, exposing sensitive data and private models to potential compromise. The prevalence of shadow AI—unauthorized or unmonitored AI tools used within organizations—has become a significant blind spot for security teams, as employees increasingly adopt generative AI tools like ChatGPT and Gemini without official oversight. This unregulated use heightens the risk of data leakage and undermines established security controls. Simultaneously, threat actors are leveraging AI to enhance spear phishing campaigns, targeting IT leaders with highly convincing, context-aware messages that are difficult to detect. Security teams are also adopting generative AI to improve open-source intelligence (OSINT) gathering, using these tools to expand keyword searches and identify evolving threat actor slang. The convergence of AI-driven attack techniques and the widespread exposure of credentials underscores the urgent need for organizations to implement robust secret scanning, monitor shadow AI usage, and adapt defenses to counter increasingly sophisticated, AI-enabled threats.
Jun 29, 2026