Skip to main content

JFrog Report Surfaces Need for Rapid DevSecOps Change in AI Era

A report published by JFrog finds that cybercriminals are now increasingly targeting the artificial intelligence (AI) tools and platforms used by application development teams.

Based on an analysis of 18.2 billion artifacts managed via the JFrog Platform, security researchers discovered 969 AI agent skills carrying high-impact payloads in addition to 495 malicious AI models on the Hugging Face platform for hosting open source AI models. Additionally, 56 malicious extensions were also discovered on the OpenVSX registry.

The survey also finds 41% of respondents work for organizations that are actively using AI libraries, with organizations on average employing 9.3 AI libraries each. At the same time, a separate global survey of 1,508 security and DevOps professionals conducted by JFrog finds more organizations are struggling to secure code generated by AI coding tools. Nearly half of respondents (45%) said reviewing and hardening AI-generated code is now a major time drain, with an equal percentage of respondents reviewing AI code manually. Conversely, just under a quarter (23%) said they treat AI suggestions for fixing code as near-definitive with minimal review, compared to 63% that understand AI suggestions as starting points requiring careful review.

In fact, the JFrog report notes that despite vulnerabilities that have been well known for decades, there has been a surge in discovery of CWE-79 (XSS), CWE-89 (SQL Injection), and CWE-74 (Injection) vulnerabilities since the dawn of AI coding.

Paul Davis, Field CISO for JFrog, said the report makes it clear that in the age of AI there is a need for fundamental changes to be made to existing DevSecOps workflows that remain uneven at best. The survey, for example, finds that 59% of respondents are trying to enforce security at the developer workstation level, while 58% enforce security at the continuous integration/continuous delivery (CI/CD) level. Another 38% are relying on platform-native security tools.

Regardless of approach, nearly half (48%) are still relying on manual processes, with the same percentage (48%) requiring a week to establish proof of compliance.

Despite that dependency on manual processes, too many organizations are overconfident in their ability to secure DevOps workflows, noted Davis. For example, nearly all respondents (97%) claim their organization has certified model governance and yet more than half (53%) self-host models from sources where malicious payloads have been detected, and 18% have zero governance over their integrated development environments (IDE) or Model Context Protocol (MCP) servers compared to 57% that at least actively curate MCP servers.

Unfortunately, the pace at which attacks are being launched against software supply chains in general only continues to increase. The JFrog report notes, for example, there was a 451% increase in malicious npm packages year-over-year, with 177,000 new malicious packages detected across registries.

Those attacks are going to increase in frequency as adversaries leverage AI to discover and exploit vulnerabilities faster, noted Davis. The challenge is that not all vulnerabilities are necessarily created equal. Two-thirds (66%) of the Common Vulnerabilities and Exposures (CVEs) analyzed by JFrog researchers had minimal real-world applicability. Only 12% were highly exploitable.

While there will undoubtedly be some major incidents in the coming year, most organizations will likely survive the onslaught, noted Davis.

The challenge, of course, is that like it or not the amount of time, effort and cost incurred making sure those incidents are kept to a minimum is now starting to rise.



from DevOps.com https://ift.tt/mSvefJ3
Labels:

Comments

Post a Comment

Popular posts from this blog

Cursor’s New SDK Turns AI Coding Agents Into Deployable Infrastructure

For most of its life, Cursor has been an IDE. A very good one. But with the public beta of the Cursor SDK, the company is making a different kind of move — one that should get the attention of DevOps teams. The Cursor SDK is a TypeScript library that gives engineers programmatic access to the same runtime, models, and agent harness that power Cursor’s desktop app, CLI, and web interface. In short, the agents that used to live inside an editor can now be invoked from anywhere in your stack. That’s a meaningful shift in how AI coding tools fit into software delivery pipelines. From the Editor to the Pipeline If you’ve used Cursor before, the workflow is familiar — you interact with an agent in real time, asking it to write functions, fix bugs, or review code. The SDK breaks that dependency on interactive use. Now you can call those same agents programmatically, from a CI/CD trigger, a backend service, or embedded inside another tool. Getting started is a single inst...
Post a Comment
Read more

Mistral Moves Coding Agents to the Cloud — and Gets Out of Your Way

For the past year or so, AI coding agents have been tethered to your local machine. You kick off a task, watch the terminal, and babysit every step. It works — but it’s not exactly hands-free. Mistral just changed that. On April 29, the Paris-based AI company announced remote coding agents for its Vibe platform, powered by a new model called Mistral Medium 3.5. The idea is simple: Instead of running coding sessions on your laptop, they now run in the cloud — asynchronously, in parallel, and without you watching over them. What’s Actually New Coding sessions can now work through long tasks while you’re away. Many can run in parallel, and you no longer become the bottleneck at every step the agent takes. That’s the core pitch. You start a task from the Mistral Vibe CLI or directly from Le Chat — Mistral’s AI assistant — and the agent handles the rest. When it’s done, it opens a pull request on GitHub and notifies you, so you review the result inste...
Post a Comment
Read more

OpenAI Debuts Symphony to Orchestrate Coding Agents at Scale

OpenAI has unveiled Symphony, an open-source specification that shifts how software development teams deploy AI in workflows, moving from interactive coding assistance toward continuous orchestration of autonomous agents. Symphony reframes project management tools as operational hubs for AI-driven coding. Rather than prompting an assistant for individual tasks, developers assign work through issue trackers, allowing agents to execute tasks in parallel and deliver outputs for human review. The change reflects a trend in enterprise AI in which systems are increasingly embedded into production pipelines rather than used as standalone tools. Symphony emerged from internal experimentation at   OpenAI , where engineers attempted to scale the use of   Codex   across multiple concurrent sessions. While the agents proved capable, human operators became the limiting factor. Engineers found they could only manage a handful of sessions before coordination overhead offset pro...
Post a Comment
Read more