All news with #software supply chain security tag

🔒 GitHub now expires newly created npm trusted publishing configurations after 48 hours if they don't complete an initial successful publish. The change validates and permanently binds the configuration only after that first publish and requires a new 48-hour window when repository or project identity changes. GitHub also blocks trusted tokens from issue_comment events and retains the existing pull_request_target restriction to reduce risks from reclaimed repository slugs.

🔒 This article explains how to deploy ML‑DSA (Module‑Lattice‑Based Digital Signature Algorithm) signing across a software supply chain using AWS services. It shows how to create an ML‑DSA certificate hierarchy with AWS Private CA, manage ML‑DSA keys in AWS KMS, and authenticate build agents with AWS IAM Roles Anywhere to sign binaries, container images, and SBOMs. The post is Part 1 of a two‑part series aimed at builders and provides practical steps, tooling notes, and operational guidance for integrating quantum‑resistant signatures today.

🔒 The npm package tensorlake, a TypeScript SDK for Tensorlake applications and cloud services, was compromised in a ChainDrop / Shai-Hulud supply chain attack after a malicious 0.5.144 release was published. The trojanized release used a preinstall hook and an obfuscated Bun-based loader to deploy a credential-stealing worm that harvests secrets, drops additional malware, establishes persistence, and enables remote code execution. Affected users are urged to remove the package and rotate exposed credentials.

🔍 In this analysis, the author argues that enterprises should avoid running separate bill-of-materials (BOM) programs for software, cryptography, AI models, authorization and runtime artifacts. Instead, organizations need a federated evidence graph that links domain-specific records via a common envelope and relationship semantics so incident responders can answer cross-cutting questions about affected products, exposure and remediation. The piece details standards, pilot steps and governance to ensure accuracy, trust and least-disclosure practices.

🛡️ Checkmarx has identified a malicious npm package, indexed-btree, that concealed its payload inside application code rather than using lifecycle scripts, indicating attackers are adapting to npm's install-time protections. The package, first published on June 18, 2026, accumulated millions of downloads before removal and is estimated to have generated roughly €230,933.57 in cryptocurrency for the operator. The loader was embedded in a BTree.prototype.set() method and used EtherHiding and blockchain-hosted encrypted blobs to fetch staged payloads before cleaning up traces.

🛡️ CloudSEK reported a supply chain attack where an attacker used a maintainer account to publish a malicious loader, GHAPPIER, in a legitimate npm package with valid provenance. The attacker altered workflows to auto-publish via GitHub Actions OIDC and Sigstore attestation, allowing a malicious release to pass npm audit signatures. The loader triggered a multi-stage chain ending in a ephemeral remote shell and was present briefly in version 0.2.21; CloudSEK found extensive reuse across repositories and recommends pinning and workflow monitoring.

🛡️ WordPress has introduced an automated security review for every plugin release before distribution via the WordPress.org update API to detect potential vulnerabilities and malicious code. The system, part of the Protect The Shire initiative, uses AI models and Jetpack Scan during a cooldown period to produce a security score; high-risk releases are blocked automatically. Developers are notified by email only when a release is blocked and must address findings to republish.

🔧 Over six months Chainguard doubled its output from 500 million to over 1 billion container build manifests, surpassing 3,000 images and 675,000 versions. The article explains what a build manifest represents and how Chainguard OS and Chainguard Factory produce continuous, reproducible artifacts with SLSA Level 3 provenance, Sigstore signatures, and SBOMs. It describes the transition from an event-driven Factory to Factory 2.0 (DriftlessAF), which uses continuous reconciliation, redundant work queues, and targeted AI to remove toil and accelerate rebuild velocity. The piece argues that faster rebuilds are essential to staying ahead of AI-enabled attackers and outlines future expansion and open sourcing of DriftlessAF.

🔍 Unit 42 details how supply chain attacks have escalated, shifting adversaries from finished applications to the developer tooling and CI/CD pipelines that build software. The report examines incidents like ChainDrop, Axios, and Shai-Hulud to show how malicious preinstall scripts, account hijacks, and memory scraping steal credentials and self-propagate. It argues that SBOMs alone are insufficient and recommends continuous visibility, execution controls, ephemeral CI servers, and short-lived credentials to stop autonomous malware.

🔒 The Linux Foundation, OpenSSF and 20+ founding members launched the Akrites coalition to defend open-source software from AI-enabled threats. Members include major AI labs, cloud providers, cybersecurity vendors and enterprises, each contributing engineers and fees. Akrites will create a shared SIRT and a standardized CVD process, with tooling based on CMU’s VINCE and LLM-driven capabilities for deduplication and patch creation. The platform is expected to go live and accept automated reports in September.

🔒 AWS Security Hub Extended has added Supply Chain Security as its tenth curated category, expanding the program to 23 partners. The launch features Chainguard and Socket as integrated partners, offering rebuilt, provenance-backed open source packages and behavioral package analysis respectively. Both offerings are available via pay-as-you-go pricing or Private Offers for committed terms, and findings flow into Security Hub in OCSF to correlate supply chain risk with other security signals. The move aims to reduce activation friction and enable cross-partner correlation across endpoint, identity, cloud, and more.

🔍 Sonatype finds enterprise applications now contain 4.31 times more critical and high-severity vulnerabilities since AI-driven software development accelerated. The firm analyzed four years of development data and reports application creation has increased nearly fivefold in the AI era. While the median age of unresolved vulnerabilities has fallen 59%, indicating faster fixes, the growth in risk outpaces traditional security processes.

🔍 Open Source's informal era is ending as enterprises and regulators demand accountability, continuity, and demonstrable maintenance. The community will split: projects that adopt enterprise-grade practices—reachable maintainers, disclosure paths, and continuous proof-of-life—and projects that remain community-driven without those guarantees. Vendors and foundations will increasingly provide contracts, long-term support, and retirement pathways to bridge gaps while the free, volunteer-led ecosystem continues alongside.

🛡️ Self‑propagating malware dubbed ChainDrop has compromised over 1,300 npm packages, collectively serving about 2 billion monthly downloads. The attacker gained access by compromising a maintainer’s GitHub account, pushed malicious code to main branches, and used legitimate GitHub Actions workflows to publish tainted releases with valid provenance. The payload uses a Bun runtime to execute an obfuscated infostealer that harvests developer and cloud credentials, then exfiltrates them to a public GitHub repository. Security vendors recommend treating affected workstations and CI/CD runners as compromised, rotating tokens, rebuilding from clean backups, and applying dependency allowlisting and provenance checks.

🔒 Google Threat Intelligence Group and Mandiant outline recent trends in large-scale open source supply chain compromises observed in 2025–2026 and provide practical mitigation and hardening recommendations. The post highlights actor techniques such as repository compromise, malicious package injection, and abuse of CI/CD triggers, and emphasizes increased risk from AI-enabled workflows. It recommends inventories, SBOMs/ABOMs, SDLC threat modeling, active risk monitoring, and configuration controls to reduce exposure.

🔒 This post explains a simple one-line configuration to add a dependency cooldown for npm and pip on Amazon Linux, instructing package managers to skip versions published in the last 24 hours. It outlines why the initial hours after publication are highest risk, summarizes recent supply chain incidents, and shows how to set and override the cooldown for security updates. The guidance includes commands for Node.js 24 and Python 3.14 on Amazon Linux 2023 and notes lockfile behavior and audit-based exceptions.

🔒 GitHub introduced a three-day cooldown in Dependabot that delays version-update pull requests for at least 72 hours after a release by default, while security updates continue to be issued immediately. The cooldown is configurable via dependabot.yml, letting teams set a different interval to suit their workflows. GitHub framed the change as a mitigation against short-lived poisoned package releases that spread quickly before removal, and recommended it be used alongside other defenses such as lockfiles and scoped tokens.

🛡️ GitHub and PyPI have implemented time-based defenses to reduce supply chain attack risk. GitHub’s Dependabot now defaults to a 72-hour cooldown before applying package updates, while PyPI blocks adding new files to releases older than 14 days. These measures aim to limit the impact of token or workflow compromises and complement other best practices such as lockfiles and restricted tokens.

🔒 CISA and four international cybersecurity agencies have issued joint guidance urging software vendors and online service providers to establish coordinated vulnerability disclosure (CVD) programs. The guidance outlines how to publish clear disclosure policies, maintain communication with researchers, and handle reports for software, hardware, and network products. It supports CISA’s Secure by Design initiative and emphasizes prioritization, exploitability-based assessment, and validating compensating controls when patches are unavailable.

🐍 This report examines how the convenience and popularity of Python have attracted supply chain abuse, showing how malicious packages can execute code during installation and persist via .pth files or sitecustomize hooks. It outlines the installation layers (hosting, installation, environment), distribution formats (sdist, wheel), and common abuse techniques, emphasizing the rapid impact of compromised packages on development and enterprise assets.