Search: “software-supply-chain”

Measuring the Security of the Evolving Software Supply Chain: a Research Agenda

Researchers propose a unified cross-ecosystem measurement agenda for software supply chain security, targeting dependency modeling and AI-generated dependency patterns.

The paper argues that existing quantitative measurement and vulnerability management approaches for software supply chain security are fragmented and ecosystem-specific, limiting comparable risk assessments. It lays out a research agenda starting with a Systematization of Knowledge to expose gaps in dependency modeling, transitive dependency treatment, and real-world exploitability of vulnerabilities. It further warns that AI-assisted development with coding LLMs will create dependency patterns not captured by traditional Software Composition Analysis tools, motivating a rethink of dependency modeling.

arXiv cs.CR·Sep 8, 14:37 UTC · 8d agoResearch

Connecting the Dots: Securing the Overlooked Corners of the Software Development Lifecycle (SDLC) Supply Chain

Unit 42 warns attackers increasingly target CI/CD pipelines and developer tools rather than application code, urging full SDLC supply chain visibility.

Palo Alto Networks Unit 42 research argues attackers are shifting focus from application code to overlooked corners of the software development lifecycle supply chain, including CI/CD pipelines and developer tooling. The write-up calls for total SDLC visibility and strict security controls to defend these developer-facing attack surfaces.

Palo Alto Unit 42·Aug 21, 23:00 UTC · 25d agoResearch in the wild

Chainloop: Open-source evidence store and policy engine for the software supply chain

Help Net Security·Aug 10, 00:00 UTC · Aug 10, 2026Policy & legal

Closing the Blind Spot: Securing Personal Repositories in the Software Supply Chain

Wiz highlights personal developer repositories as a supply chain blind spot leaking corporate secrets, offering correlation-based risk validation and remediation.

Wiz argues that developers' personal code repositories are a blind spot in software supply chain security where corporate secrets quietly escape. The company describes an approach that correlates personal repositories to specific developers, validates the actual risk, and drives remediation. No specific incident or vulnerability is disclosed in the announcement.

Wiz Blog·Aug 13, 13:48 UTC · Aug 13, 2026Tools2

LiteLLM Supply-Chain Attack - Technology, Banking and Healthcare the Most Affected

TeamPCP planted the SANDCLOCK credential stealer in LiteLLM PyPI releases, exposing credentials across 2,038 repositories at 898 organizations including Microsoft and NVIDIA.

Threat actor TeamPCP compromised LiteLLM maintainer credentials and published malicious versions 1.82.7 and 1.82.8 to PyPI around March 2026, creating an exposure window of several months. The SANDCLOCK credential stealer exposed full credential sets across 898 GitHub owners and 2,038 repositories, including Microsoft, Azure, IBM, NVIDIA, PayPal, Deloitte, Bosch, and S&P Global. Stolen material includes GitHub CI/CD identities, AWS/GCP/Firebase credentials, SSH keys, Kubernetes secrets, and OpenAI and Anthropic API keys; Resecurity acquired a 150GB archive with 2,146 credential records. Technology, banking/finance, and healthcare organizations are the most affected sectors, and victims must rotate all exposed credentials.

Security Affairs·Aug 17, 17:09 UTC · Aug 17, 2026Malware in the wild

ATM Flaws Reveal Key Weaknesses in the Software Supply Chain

A researcher disclosed nine vulnerabilities in ATM encryption and authentication software, highlighting weaknesses across the software supply chain.

WIRED reports that a security researcher found nine vulnerabilities in software used for ATM encryption and authentication. The disclosure matters beyond cash machines because the affected components illustrate broader weaknesses in the software supply chain. The article does not report active exploitation of the flaws.

WIRED · Security·Aug 31, 10:00 UTC · 16d agoVulnerability

VEX-Bench: Benchmarking LLM Agents for Assessing Exploitability of Software Supply Chain Vulnerabilities

Introduces VEX-Bench, 75 expert-labeled real-world cases testing whether LLM agents can assess supply chain vulnerability exploitability; frontier models reach about 80% F1.

VEX-Bench is the first benchmark evaluating LLM agents on assessing whether upstream dependency vulnerabilities are exploitable in downstream projects, with 75 real-world expert-labeled cases across Python, Java, and Go mined from GitHub. Nine models across three agent harnesses were evaluated; GPT-5.5 and Claude Opus 4.6 reach approximately 80% F1 on binary vulnerability-status classification, but only GPT-5.5 surpasses 70% macro-F1 on fine-grained justification classification. The gap highlights the difficulty of moving beyond binary exploitability calls to explaining exploitability reasons, unlike prior benchmarks targeting zero-day settings.

arXiv cs.CR·Sep 7, 22:52 UTC · 8d agoResearch1

Facilitating AI integration with simplicity at scale

Jabil's SAP IT director says simplifying integration across 100+ sites in 30+ countries with SAP Integration Suite created the data backbone for AI.

In an MIT Technology Review Business Lab podcast produced in partnership with SAP, Jabil SAP IT director Harish Manohar described consolidating fragmented tools across more than 100 sites in over 30 countries using SAP Integration Suite. The manufacturer, with 140,000-plus employees and more than 400 top-brand customers, says a standardized data backbone enables real-time supply chain visibility and is a prerequisite for scaling predictive, AI-driven planning and forecasting. The company frames simplification-first modernization as a competitive advantage tied to measurable business value and operational resilience.

MIT Technology Review · AI·Sep 2, 14:00 UTC · 14d agoAI industry1

Propagation Model for SSC attacks: Why SBOM (tools) don't tell the whole truth

Study shows open-source SBOM tools only cover structural exposure and vulnerability presence, missing code reachability and taint-path analysis stages.

An arXiv paper proposes a four-stage propagation model for software supply chain attack effects and empirically evaluates four open-source SBOM tools against it using three projects and the Log4j vulnerability as the test case. Current SBOM tools systematically support only Stage 1 (structural exposure) and Stage 2 (vulnerability class presence), while Stage 3 (code reachability) and Stage 4 (taint path analysis) require capabilities absent from the SBOM ecosystem. The authors argue propagation-centred SSC security research is needed to prevent cyber risk from evolving into systemic risk.

arXiv cs.CR·Sep 4, 17:31 UTC · 12d agoResearch1

Claude, Codex, and Hermes installed unowned code inside corporate networks

Analysis found 227 install commands from Claude, Codex, and Hermes agents inside corporate networks pointing to packages with no verifiable owner.

Researchers found 227 install commands issued by the AI coding agents Claude, Codex, and Hermes inside corporate environments, with the referenced packages having no clear owner. The finding highlights agentic software supply-chain risk, as AI agents can pull unverified third-party code into production networks without organizational oversight. The article is published in Ars Technica's security section and frames this as an emerging governance gap for AI-driven development.

Ars Technica · Security·Aug 27, 14:00 UTC · 20d agoAI safety & security in the wild2

Bitsight connects threat intelligence and exposure monitoring across the supply chain

Bitsight made Beacon generally available, combining supply-chain exposure monitoring with MCP support to feed threat intelligence into AI workflows.

Bitsight announced general availability of Beacon, which continuously monitors critical vendors for exposure, vulnerabilities, malicious activity, intrusion, stolen credentials and compromise. New Model Context Protocol (MCP) and agentic capabilities push Bitsight intelligence into AI-enabled workflows, with over 400 customers signing up for early access in one month. The company cites data that third parties now account for almost half of enterprise breaches, up over 60% year over year.

Help Net Security·Sep 14, 13:42 UTC · 2d agoTools

Mines, Minds, and Machines: The Journey of AI

Recorded Future essay traces AI's supply chain from minerals and chips to embodied AI, mapping geopolitical rivalry and cyber operations at every stage.

Recorded Future published an analysis following the supply chain of the fourth industrial revolution: minerals become chips, chips become data centers, and data centers become models that are acquiring physical capabilities. It argues geopolitical rivalry and cyber operations now run along every link, from mine to embodied AI machines.

Recorded Future·Aug 11, 00:00 UTC · Aug 11, 2026AI industry

Threat Brief: 3CXDesktopApp Supply Chain Attack (Updated)

Trojanized 3CXDesktopApp installers for Windows and macOS loaded RC4-encrypted shellcode delivering a backdoor to hundreds of thousands of 3CX users.

Threat actors compromised the 3CXDesktopApp build process, adding malicious libraries (ffmpeg.dll, d3dcompiler_47.dll) to installers downloaded from the developer's website. The Windows MSI loader decrypts embedded shellcode with RC4, sleeps for a random 1-4 weeks, then beacons to C2 hidden in icon files on GitHub. Unit 42 fingerprinted 247,277 IPs across 199 countries using 3CX applications and blocked shellcode execution at 127 Cortex XDR customers between March 9-30, 2023.

Palo Alto Unit 42·Aug 17, 12:18 UTC · Aug 17, 2026Threat actor in the wild1

AI supply chain risk is showing up in developer workflows first

Zentera Systems CEO says AI supply chain attacks currently hit developer workflows first, advising segmentation over tooling and citing the Phantom Raven campaign.

In an interview, Zentera Systems CEO Dr. Jaushin Lee argues that most active AI supply chain incidents target developer workflows and open-source package repositories, while poisoned model weights, compromised MCP servers, and poisoned vector stores remain largely in research and demos. He cites the active 'Phantom Raven' campaign, where attackers register AI-hallucinated package names in public repositories with malicious payloads that silently infect vibe-coding build pipelines. He recommends software-defined segmentation, semiconductor-style project enclaves with egress controls, and warns that self-hosting models without agent sandboxing leaves exposure unchanged.

Help Net Security·Aug 25, 00:00 UTC · 22d agoAI safety & security

Nvidia and Palantir team up to run supply chains with AI, starting with Nvidia's own million-part operation

Nvidia and Palantir integrated open Nemotron models and cuOpt into Foundry to run AI-driven supply chains, starting with Nvidia's million-part operation.

Nvidia and Palantir announced a partnership to run supply chains with AI, first deployed on Nvidia's own network of millions of parts and thousands of suppliers; a single Vera Rubin rack contains 1.3 million components. Palantir is integrating open Nemotron models into its Foundry platform for customer fine-tuning, while Nvidia cuOpt handles scenario planning and optimization, with decisions fed back to improve models over time. The stack runs on customer hardware or in the cloud through the Sovereign AI OS reference architecture with infrastructure partners Dell, Cisco, Rackspace, and Nebius, with more details shown at AIPCon 11.

The Decoder·Sep 10, 12:23 UTC · 6d agoAI industry1

North Korean Hackers Tied to Rust Supply Chain Attack

Researchers linked a backdoor hidden in compromised Rust packages to North Korean actors' prior software supply chain attack campaigns.

Cybersecurity researchers attributed a malicious backdoor planted in compromised Rust packages to North Korean threat actors based on ties to earlier supply chain attacks. The campaign targets the open-source developer ecosystem, where infected packages can propagate downstream to developer build systems. The attribution suggests DPRK-aligned actors continue investing in open-source supply chain tradecraft.

Infosecurity Magazine·Aug 21, 12:40 UTC · 26d agoThreat actor in the wild

Two alleged TeamPCP members arrested and charged after months of software supply

Australian Federal Police, with FBI support, arrested two alleged TeamPCP members behind supply-chain attacks that compromised over 1,000 organizations.

The AFP charged two Western Australian men, identified by media as Ruben Ian Thomson (21) and Louis Michael Gaebler (23), with 14 combined offences including unauthorized data modification and dealing in criminal proceeds. TeamPCP is blamed for poisoning open-source software releases including Trivy, LiteLLM, and the mini Shai-Hulud worm campaign, exposing over 500,000 credentials and at least 300 GB of data. Victims included the European Commission and GitHub, with remediation costs estimated in the hundreds of millions of dollars. Researchers from Flare traced one suspect through leaked passwords, a GitHub alias, and a Steam profile.

CyberScoop·Aug 27, 14:32 UTC · 20d agoPolicy & legal1

Risks in IoT Supply Chain

Unit 42 analyzes multilayer IoT supply chain risks across hardware, firmware, and software, citing counterfeit Cisco switches and OpenWrt attacks.

Unit 42 examines weaknesses in the IoT supply chain ecosystem across hardware, firmware, operation, and vulnerability layers, noting that 89% of IT decision-makers reported IoT device growth and IDC forecast 41.6 billion connected IoT devices by 2025. Examples include counterfeit Cisco Catalyst 2960-X switches with possible backdoor access (F-Secure, July 2020), a March 2020 OpenWrt flaw enabling malicious update impersonation, and threat actor interest in TeamViewer remote support software. The report stresses that untracked third-party components and missing device inventories make it hard to assess vulnerability impact across vendors.

Palo Alto Unit 42·Aug 19, 12:05 UTC · 28d agoResearch

Supply Chain Attacks in 2026: Why Threat Intelligence Is the Only Early Warning System That Works

Cyble argues supply chain attacks are a primary breach vector, citing Verizon DBIR third-party figures and CISA SBOM guidance to pitch its TPRM platform.

Cyble's vendor blog frames third-party compromise as a first-order breach risk, citing Verizon's 2026 DBIR finding that third parties were involved in 48% of breaches, up 60% year over year. It recounts the Cl0p campaigns against Progress MOVEit Transfer (CVE-2023-34362), which affected over 2,700 organizations and 93 million people, and Fortra GoAnywhere (CVE-2023-0669) with roughly 130 claimed victims. It also highlights CISA and NSA's 2026 Minimum Elements for a Software Bill of Materials covering open-source, AI, and SaaS components. The piece concludes by promoting Cyble's Third-Party Risk Management platform.

Cyble·Sep 3, 08:21 UTC · 13d agoIndustryCVE-2023-34362CVE-2023-0669

Wicked Problem, Parsimonious Solution: Securing Electric Vehicle Charging Station Software

Position paper proposes hierarchical software quality assurance to characterize and secure EV charging station software attack surfaces.

The authors argue that charging station supply-equipment software is a largely unprotected and poorly characterized attack surface in EV charging infrastructure. They advocate applying hierarchical software quality assurance (HSQA) to this specialized software, spanning from individual vulnerabilities such as CVEs to high-level characteristics like the CIA Triad. HSQA embeds quality and security considerations across the entire software development lifecycle to assess and improve charging station software security.

arXiv cs.CR·Sep 9, 17:37 UTC · 7d agoResearch