AI Adoption in Software Development Increases Cybersecurity Risks
A surge in the use of AI-powered coding and automation tools is reshaping software development and cybersecurity practices, with recent industry reports highlighting a significant rise in vulnerabilities and incidents linked to AI-generated code. Surveys of security professionals and executives reveal that a substantial portion of production code is now written by AI, but security guardrails and oversight have not kept pace, leading to new flaws and uncertainty over accountability when breaches occur. Despite optimism about AI's future capabilities, most organizations have already experienced negative impacts, and only a small fraction of CEOs express confidence in their AI systems' ability to protect sensitive data.
The rapid adoption of AI has also intensified the overall cybersecurity threat landscape, as cybercriminals leverage AI to accelerate attack timelines and enhance social engineering tactics. Notably, there has been a dramatic increase in voice phishing attacks and a reduction in attacker breakout times, underscoring the urgency for stronger governance, training, and formal controls around AI use. Security leaders are urged to prioritize data integrity, secure AI supply chains, and integrate security into AI development processes to address these evolving risks.

Get ahead of threats like this
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
How this story unfolded
4 events from the most recent confirmed update back to the earliest known activity.
Cloudsmith report details AI code oversight and supply chain security gaps
Cloudsmith's 2026 Artifact Management Report found widespread adoption of AI-generated code but weak security validation, limited auditing, and poor provenance tracking for AI-related artifacts. The report warned these shortcomings increase software supply chain and compliance risk, including difficulty producing SBOMs and provenance documentation under emerging regulations.
Further reporting compares AI coding output to junior developers
On October 27, 2025, additional coverage said AI-generated code often resembled junior developer output and was contributing to ongoing code security risks. This expanded the narrative around AI-assisted development creating persistent application security challenges.
Analysis warns AI-generated code is creating security cleanup work
Reporting on October 24, 2025 said software produced with AI tools was introducing quality and security issues that human developers and security teams then had to remediate. The event reflects public disclosure of concerns about AI-assisted coding practices and their downstream security burden.
Reports highlight AI adoption increasing cybersecurity strain
Industry reporting in late October 2025 said growing enterprise AI adoption was intensifying pressure on cybersecurity teams and expanding security risk exposure. The coverage framed AI use as a broad operational and defensive challenge rather than a single incident.
Related entities
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Sources
4 references tracked. Mallory keeps watching after this page renders.
Developers are slacking on AI-generated code safety - here's why it could come back to haunt them | IT Pro
itpro.com
Open sourceAI writes code like a junior dev, and security is feeling it
helpnetsecurity.com
Open sourceWhen AI writes code, humans clean up the mess
helpnetsecurity.com
Open sourceAI adoption intensifies cybersecurity strain, report finds
scworld.com
Open sourceSee the full picture, correlated to your attack surface.
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.


