Supply Chain & Open Source
Cybersecurity news in this category
GitHub and PyPI Add Time-Based Defenses Against Supply Chain Attacks
GitHub and PyPI Introduce Time-Based Defenses Against Supply Chain Attacks
Container Image Risks: Why Skipping Verification Today Breaks Your Service Tomorrow
Should Python Libraries Raise Minimum Dependency Versions to Block Vulnerable Releases?
Seth Larson of the Python Software Foundation argues that library maintainers should not automatically raise the minimum allowed version of a dependency after a vulnerability is disclosed. He states that dependency metadata exists to declare compatibility, while security decisions belong to the application owner who controls the final build. The recommendation has sparked debate in the Python community, with some maintainers supporting the separation of concerns and others viewing security constraints as part of library support obligations. CodeScoring’s analysis examines the practical impact on the ecosystem, noting that over 10,000 packages depend on urllib3 and tens of thousands more rely on numpy, requests, and pandas. The piece concludes that version bounds may incorporate security considerations only after evaluating real usage, affected versions, and downstream compatibility, but they cannot replace application-level vulnerability management with lockfiles and tools such as pip-audit.
Corporate Nextcloud Security Gaps: Default Settings, Antivirus Failures and Open Source Integration Challenges
A detailed analysis from K2Tech reveals that corporate Nextcloud deployments require extensive security hardening beyond default open source configurations. The article examines integration with LDAP, WAF, Anti-DDoS and multiple antivirus engines including ClamAV, Kaspersky Scan Engine and PT Sandbox over ICAP. Critical issues include antivirus plugins bypassing scans during unreachable states or chunked file uploads via MOVE commands, allowing infected files to reach S3 storage. Performance tests on identical 4 vCPU and 16 GB RAM hardware showed Kaspersky Scan Engine delivering the highest throughput while PT Sandbox imposed heavy CPU loads. The piece also covers architecture spanning MariaDB Galera, Redis, Elasticsearch and multi-AZ S3, plus the need for custom parameter tuning and continuous testing due to frequent Nextcloud releases. Overall, the report emphasizes that true corporate-grade security for open source file sharing demands significant post-installation effort and monitoring.
FakeGit Campaign Floods GitHub with 7,600 Fake Repositories to Distribute SmartLoader Malware
The FakeGit operation has created or repurposed approximately 7,600 repositories on GitHub to trick users and automated agents into downloading SmartLoader, a loader that installs additional malware including the StealC infostealer. Attackers clone legitimate projects, replicate documentation and developer profiles, and host malicious ZIP files in GitHub Releases that have already accumulated over 14 million downloads across roughly 200 repositories. A notable tactic called AgentBaiting targets AI systems by disguising more than 800 repositories as AI Skills or MCP servers, leading tools from Anthropic, Google, and OpenAI to recommend malicious packages. The infection chain uses LuaJIT to execute obfuscated Lua scripts that deploy SmartLoader, which establishes persistence via scheduled tasks and resolves command-and-control infrastructure through a blockchain dead drop on Polygon. Over 600 listings linked to the campaign have also appeared on public directories such as LobeHub, Glama, and MCP Market, extending the reach beyond GitHub. Defenders are advised to maintain approved catalogs of AI components, apply application control policies, and monitor for LuaJIT execution and anomalous outbound traffic.
Securing CI/CD in Open Source Projects: Cilium’s Final Guide to Credentials, Verification, and Remaining Gaps
VK Cloud has published the third and final part of its translated Cilium series on protecting the software supply chain in open source projects. The article details how Cilium isolates CI and production credentials using separate GitHub environments, enforces keyless signing with Sigstore Cosign and SBOM attestations, and applies strict release controls that prevent compromised workflows from reaching production images. It also covers the team’s ongoing security operations, additional hardening measures such as immutable tags and mandatory DCO sign-offs, and a gap analysis against OpenSSF Scorecard and SLSA standards. The post examines GitHub’s 2026 Actions security roadmap and explains how planned platform features like dependency blocking, scoped secrets, and native egress firewalls align with Cilium’s existing controls. The piece concludes by emphasizing defense-in-depth and the importance of openly sharing supply-chain security practices across the open source community.
Understanding SCA: How Software Composition Analysis Helps Manage Software Supply Chain Risks
Software Composition Analysis (SCA) has emerged as a critical tool for organizations seeking to understand and control the risks hidden within modern applications built from third-party components, open-source libraries, container images, and transitive dependencies. SCA tools scan projects to identify components, versions, dependency chains, known vulnerabilities, and license issues, providing visibility that traditional security methods often miss. The approach supports SBOM generation and integrates with standards such as SPDX, CycloneDX, and VEX to improve transparency across the software supply chain. Organizations use SCA throughout the development lifecycle—from dependency selection and build-time gating to post-release monitoring—to reduce reaction time when new vulnerabilities appear and to manage technical debt, licensing conflicts, and abandoned packages. In regulated environments, including compliance with Russian standards like GOST R 56939-2024 and FSTEC requirements, SCA helps teams demonstrate control over software composition and prepare evidence for certification. While powerful, SCA is not a silver bullet: it relies on accurate data, cannot detect zero-days, and requires careful policy tuning to avoid alert fatigue or developer workarounds.
Cyberattack on Nichirei Logistics Group Disrupts Frozen Food Deliveries to KFC Japan and Thousands of Restaurants Nationwide
A cyberattack on Nichirei Logistics Group, Japan's largest operator of refrigerated and frozen logistics, forced the company to shut down critical systems on July 13, halting operations across its network of 140 cold storage distribution centers. The incident quickly impacted major clients including KFC Japan, which serves more than 1,300 restaurants, leading to shortages of chicken and other ingredients needed for its Original Recipe. Other affected companies include Hotto Motto, Yayoi Ken, Kura Sushi, Aeon supermarkets, and TableMark, all of which reported delivery delays or product shortages. Nichirei confirmed that personal data was stored on some compromised servers and notified Japan's data protection authority while promising to disclose any confirmed breach. The company has not identified the attackers, disclosed the intrusion method, or confirmed whether ransomware was involved, citing security reasons for withholding technical details. Recovery efforts are scheduled to begin gradually on July 17, though a full return to normal operations has not yet been announced.
No Hacker Genius Needed: One Login and 49 Minutes Suffice in Injective Supply Chain Attack
A routine update to the @injectivelabs/sdk-ts library for Injective blockchain wallets turned into a supply-chain trap within 49 minutes, stealing users' recovery phrases and private keys. The malicious version 1.20.21 was published on npm on July 8, 2026, after attackers compromised a long-trusted maintainer account and pushed code directly to the main branch. The backdoor, disguised as anonymous performance statistics collection, activated only when applications called PrivateKey.fromMnemonic() or PrivateKey.fromHex(), exfiltrating sensitive data via the X-Request-Id header to an attacker-controlled server mimicking Injective infrastructure. Eighteen Injective Labs packages were affected, with 87 downstream dependencies also pulling in the compromised library, which sees roughly 175,000 monthly downloads. Although developers rolled back the changes and released clean version 1.20.23 within 49 minutes, at least 310 malicious downloads were recorded, and cached copies may persist in build environments. Security researchers from Datadog, Socket, StepSecurity, and OX Security have advised immediate migration to the patched release and full key rotation for any wallets that interacted with the tainted code.