Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

On July 14, 2026, attackers compromised release processes connected to the AsyncAPI open- source project and published malicious versions of four widely used npm packages with a combined reach of approximately 2.9 million weekly downloads.

Supply chain attacks are having a moment. Open-source malware detections jumped 73% in 2025. In the past year, the debug and chalk packages were backdoored, the tj-actions GitHub Action was compromised and pulled malicious code into thousands of pipelines, and the axios maintainer account was hijacked and used to distribute a RAT. Malicious releases also hit Zapier, ENS Domains, PostHog, and Bitwarden CLI. Every one of these attacks was preventable with controls that were available at the time.

This CISO Executive Briefing analyzes material developments over two horizons: the past week (July 1–7, 2026) and the past month (June 8–July 7, 2026). Analysis draws exclusively from verified public disclosures, regulatory filings, threat intelligence platforms, and incident reporting. Focus areas include AppSec posture, software supply chain integrity, identity and contractor risk, cloud/IaC exposure, and the accelerating integration of AI into attacker TTPs.

There’s a category of security risk that most organizations aren’t ready for. It doesn’t live in your code repository, your CI pipeline, or your developer laptops. It lives in your runtime, in the autonomous AI agents already running in your environment, extending their own capabilities, and making decisions that no human explicitly approved. This is the challenge JFrog set out to address with our integration with NanoCo AI and their open-source agent framework, NanoClaw.

If an attacker compromised a dependency buried three levels deep in your build pipeline tonight, how long would it take you to find out? Open source libraries, third-party frameworks, transitive dependencies, build tooling, and now AI-generated code that developers may not have reviewed line by line: each of these components flows into your application, whether your team explicitly chose it or not. Each component is a potential entry point.

It’s official. Gartner just published the very first Gartner Magic Quadrant for Software Supply Chain Security, and JFrog has been recognized as a Leader, placing highest for Ability to Execute among all the vendors included. For an inaugural report in a category this important, that placement means a great deal to us, and we don’t take it lightly.

May 2026 will be remembered as the month the AI developer toolchain itself became the primary attack surface. A single threat actor — TeamPCP — ran a nine-day campaign that started as a worm in open-source packages, escalated through a poisoned code-editor extension, and ended inside GitHub’s own infrastructure.

Quick answer: Today’s supply chain disruptions stem from surging demand for components, especially server CPUs feeding the AI build-out, rather than the pandemic-era shutdowns of 2020 and 2021. Companies can protect themselves by diversifying suppliers, locking in pricing terms early, holding strategic inventory, and investing in real-time visibility tools. Think of your supply chain like the plumbing in an old building. When everything flows, you never think about it.