Loading story…
Multiple studies and industry reports found that AI-generated or "vibe-coded" software is frequently shipped with serious security flaws, including XSS, SQL injection, hardcoded secrets, unsafe eval usage, weak authentication logic, wildcard CORS, exposed .env data, and insecure dependencies. One analysis of 5,600 publicly accessible AI-built applications reported more than 2,000 high-risk vulnerabilities and over 400 exposed secrets, while a separate review of 549 self-described AI-generated repositories found widespread committed secrets, injection issues, hardcoded passwords, and other common sanitization failures. Veracode and other researchers similarly warned that code produced by large language models often maps to OWASP Top 10 weakness classes and that repeated AI-assisted edits, poor prompts, and excessive agent permissions can further increase risk.
At the same time, researchers and vendors highlighted both the promise and fragility of AI-assisted security tooling. Trail of Bits reported that OpenAI Codex goal-based prompting helped uncover previously unknown bugs in projects including Rust, curl, zlib, and Keycloak, but stressed that human experts were still needed to scope goals, validate findings, and handle disclosure. New academic work also showed that LLM-based vulnerability detectors can be easily misled: the ALIBI framework used adversarial code comments to evade four detectors with success rates above 90%. In response to growing concern over agent reliability, Amazon backed the Lean language project to strengthen formal verification for AI agents, while security experts argued that theorem proving can improve assurance for high-risk components but should be applied selectively as part of broader defense-in-depth.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
5 events from the most recent confirmed update back to the earliest known activity.
Amazon announced on 26 July that it would provide substantial long-term financial support to the Lean Focused Research Organization, citing Lean's strategic importance for AI agent safety and formal verification. The company also said it already uses Lean-based verification in Bedrock AgentCore, AWS Clean Rooms' SampCert, AWS Neuron, and Aurora protocol verification.
A researcher published an r/netsec analysis of 549 self-described AI-generated repositories, after initially considering 577 and excluding 28 for size or availability. The study reported frequent issues including committed secrets, high-severity findings, injection-related problems, wildcard CORS, and hardcoded passwords, and released anonymized per-repository JSONL results.
Trail of Bits disclosed that its /goal-based autonomous bug-hunting workflow used during Patch the Planet found previously unknown issues in projects including Rust, curl, zlib, and Keycloak. The post says some Rust bugs were later patched in Rust 1.98 and that one variant-hunting effort reported nine bugs, three already fixed and merged upstream.
An arXiv paper introduced ALIBI, a black-box attack framework that uses adversarial code comments to evade LLM-based vulnerability detectors. The authors reported over 90% attack success across four detectors when tested on 125 real-world null-pointer dereference vulnerabilities.
Research cited in the source reported that scans of 5,600 publicly accessible AI-generated applications found more than 2,000 high-risk vulnerabilities and over 400 exposed secrets, indicating that roughly one in three projects was publicly deployed with exploitable flaws.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
10 references tracked. Mallory keeps watching after this page renders.
infoworld.com
Open sourceinfoworld.com
Open sourcethenewstack.io
Open sourcereversinglabs.com
Open sourcereddit.com
Open sourcearxiv.org
Open sourceveracode.com
Open sourcecodeby.net
Open sourceMap 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.
Two new studies found that AI-generated application code frequently contains exploitable vulnerabilities, with risk varying sharply by model, framework, and application size. Secure Code Warrior said testing of 1,760 complete codebases produced by 16 frontier models uncovered more than **27,000 vulnerabilities**, averaging **15 confirmed flaws per codebase** and **4.3 critical or high-severity issues**. Researchers said no single model was consistently safest across all environments; instead, each model showed a repeatable security fingerprint, with recurring **OWASP** weakness patterns and common omissions such as authentication checks and input validation. Xint.io separately identified **434 exploitable flaws** in AI-generated or AI-hardened applications, reporting that denial-of-service and resource exhaustion bugs, authorization failures, insecure direct object reference, and traversal or **SSRF** issues were common. The most severe findings were tied to hardcoded or default secrets and debug-mode remote code execution, while authorization weaknesses worsened as application size increased, particularly in a larger brownfield **Gnuboard7**-based app. Both reports said organizations should expect continued AI-assisted development and strengthen security review around recurring weaknesses such as hard-coded credentials, sensitive data leakage into logs, cross-site scripting, predictable session tokens or reset codes, and path traversal.
Jul 24, 2026
Security researchers and vendors documented rapid progress in using large language models and autonomous agents for offensive security testing, from early machine-learning-driven exploitation in **Deep Exploit** to newer multi-agent systems such as **BLADE** and Mastra-based workflows. In controlled demonstrations, these systems automated parts of reconnaissance, privilege-escalation analysis, credential discovery, lateral movement, and reporting, while broader evaluations found modern models increasingly capable of code understanding, vulnerability reasoning, and black-box web assessment tasks. The reporting also highlighted industry milestones such as AI-assisted pentesting tools reaching top bug bounty rankings and the growing use of agent patterns including **ReAct**, **Plan-and-Execute**, and orchestrated multi-agent designs for security assessments. At the same time, the same body of work warned that AI-for-security deployments are creating new attack surfaces. Researchers observed internet scanning for exposed OpenAI-compatible `Chat Completions` endpoints, with likely goals including fingerprinting LLM servers, abusing unauthenticated inference, causing denial of service, and reaching downstream integrations such as **RAG**, tool calling, and URL fetching. Separate analysis warned that long-term memory in AI agents can preserve attacker-influenced instructions, stale conclusions, or misleading context across sessions, making provenance, freshness, access control, correction, and deletion critical controls. Across the studies, the message was consistent: AI agents are becoming more useful for security operations and testing, but their deployment requires strict governance, authentication, and safeguards against prompt injection, unstable execution, and low-quality automated findings.
Aug 15, 2026
Security leaders are warning that **AI agents are increasingly operating as “digital employees”** inside enterprise workflows—triaging alerts, coordinating investigations, and moving work across security tools—often with **broad permissions and limited governance**. The core risk highlighted is that organizations are deploying high-authority agents like plug-ins (reused service accounts, overbroad roles, weak oversight), creating fast-acting operators that can be manipulated and that lack the contextual judgment and policy awareness expected of human staff. Related commentary also raises concerns about **AI-to-AI communication** and “non-human-readable” behaviors that could reduce auditability and complicate investigations and control enforcement. In parallel, public examples show how quickly AI can accelerate **vulnerability discovery**: Microsoft Azure CTO Mark Russinovich reported using *Claude Opus 4.6* to decompile decades-old Apple II 6502 machine code and identify multiple issues, underscoring that similar techniques could be applied to **embedded/legacy firmware at scale**. Anthropic has also cautioned that advanced models can find high-severity flaws even in heavily tested codebases, reinforcing the likelihood that both defenders and attackers will leverage AI for faster bug-finding. Separate enterprise IT coverage notes that organizations are **reallocating budgets toward AI** by consolidating tools and renegotiating contracts, which can indirectly increase security exposure if cost-cutting reduces overlapping controls or if AI adoption outpaces governance and identity/access management maturity.
Jun 29, 2026