appsec.fyi › Supply Chain Security

Supply Chain Security Resources

Page 5 of 17: resources 201–250 of 840, added Jun 2026 to Jul 2026.

The newest Supply Chain Security resources are on the Supply Chain Security page. For a reading order instead of a date order, see the Supply Chain Security learning path.

Date AddedLinkExcerpt
2026-07-25 2026Government orders GitHub to remove Bluetooth-based chat app Bitchat: Jack Dorsey news 2 min readNotice regarding the Indian government's order to GitHub to remove the Bluetooth-based chat application Bitchat. The Indian Cybercrime Coordination Centre cited concerns that Bitchat's decentralized, anonymous communication, without mandatory registration or centralized logging, poses a substantial risk of misuse by anti-national elements, terrorist organizations, and cybercriminals seeking to evade lawful detection. The application, which functions without mobile networks or internet, impedes law enforcement's ability to intercept, attribute, and investigate communications, particularly during network restrictions or public disorder situations. The order references violations of Sections 43, 84B, and 84C of the IT Act and Section 61 read with 196 and 197.
2026-07-24 2026Trump Orders Defense Contractors to Map Software Suppliers Across Critical Supply Chains news 5 min readExecutive Order mandates defense contractors meticulously map critical supply chains, including software and technology, to national security systems, extending beyond traditional SBOMs to trace origins from raw materials. This requires proactive supplier vetting, identification and reporting of significant risks to the Department of War within 15 days, and mitigation plans. The order anticipates the government using AI for supply chain analysis, potentially creating new security targets and expanding cybersecurity and third-party risk team responsibilities. → securityweek.com
2026-07-23 20264 ways to secure local developer IDEs and tools without sacrificing velocity beginnerThis article outlines four methods to enhance the security of local developer IDEs and tools without compromising workflow speed. The focus is on practical strategies that integrate seamlessly into the development process, ensuring that security measures don't become a bottleneck. The core idea is to balance robust security with the need for efficient development. The linked content likely explores actionable advice for developers to protect their local environments. → cybersecuritydive.com
2026-07-23 2026The Streak Continues: Four More Supply Chain Attacks Hit npm and PyPI news 6 min readAnalysis of four recent supply chain attacks—Miasma/Hades worm on npm and PyPI, fake payment SDKs stealing CI secrets, a stolen npm token poisoning Jscrambler, and a hijacked CI pipeline for AsyncAPI—highlights attackers targeting credentials in developer environments. These incidents reveal evolving tactics, including bypassing install script protections by executing payloads on import, and compromising CI identities to produce seemingly valid Sigstore and SLSA provenance for backdoored packages. → blog.gitguardian.com
2026-07-22 20261 in 4 businesses hit by cyber attacks through their supply chain in the last year news 4 min readSurvey of UK businesses reveals 26% suffered supply chain cyber incidents in the last year, with many knowingly continuing to work with vulnerable suppliers. This research from Databarracks highlights persistent challenges in supply chain resilience, showing that traditional tick-box supplier assessments provide a false sense of security. Experts advise treating critical suppliers as part of one's own security perimeter, implementing multi-factor authentication, and collaborating on business continuity exercises.
2026-07-22 2026Four More Supply Chain Attacks Hit npm and PyPI news 6 min readLibrary of techniques used in recent supply chain attacks targeting npm and PyPI, including the Miasma worm, IronWorm infostealer, fake payment SDKs harvesting CI secrets, credential theft via a compromised jscrambler token, and CI pipeline hijacking in the AsyncAPI project. These attacks exploited various entry points like malicious install hooks, Python startup files, stolen publishing credentials, and CI workflow vulnerabilities to steal sensitive information such as cloud credentials, API tokens, and cryptocurrency wallets. The attacks demonstrate how attackers circumvent protections and leverage compromised CI identities to generate seemingly legitimate, yet malicious, package releases. → blog.gitguardian.com
2026-07-22 2026Signed Attested and Malicious: The Software Supply Chain Has a Deepfake Problem advanced 4 min readLibrary for detecting software supply chain "deepfakes," where malicious packages present legitimate SLSA provenance and signatures, making them indistinguishable to traditional scanners. This library focuses on behavioral analysis of package installation hooks, network calls, and version changes, alongside account activity monitoring, to identify anomalies like rapid, large-scale publishing or unexpected package behavior. It advocates for a control point between registries and developer machines, holding packages for examination before they enter the build process, and treating new versions with a holding period, as pioneered by efforts to combat worms like Miasma and Shai-Hulud. → devops.com
2026-07-22 2026Tyro's CISO: Being the "Einstein of cybersecurity" isn't enough if developers don't trust you beginner 6 min readTalk from Tyro's CISO Arun Singh on rebuilding developer trust after security control rollouts, emphasizing the need for frictionless tools like in-IDE vulnerability detection and enforceable device protection. Singh highlights how conventional advice for supply chain security, such as keeping dependencies updated, can be weaponized, leading to his team's advocacy for a 7-day package version cooldown period. The discussion stresses that developer trust is a finite resource essential for effective security strategies, especially at scale. → aikido.dev
2026-07-22 2026The Perfect Heist: NuGet Typosquat Targets Betting Platform to Rig Results intermediate 11 min readWriteup on the Newtonsoftt.Json.Net NuGet typosquat targeting Digitain, a betting platform. The malicious package, masquerading as Newtonsoft.Json, delivers a trojanized fork that rigs game results and exfiltrates data. It employs HarmonyLib to patch the `GenerateGameResult` method within `Digitain.FG.SharedCrash.GameLogic.SharedCrashRules`, with payload evolution across seven versions featuring obfuscation changes, rigging strategies, and exfiltration paths, utilizing the header `X-Seq-ApiKey: theperfectheist2025`. The package was available on NuGet from August to October 2025. → jfrog.com
2026-07-21 2026Why Developer Password Hygiene Is a Software Supply-Chain Issue beginnerDeveloper password hygiene is a critical software supply chain issue. Weak or reused passwords, exposed credentials, and inadequate access controls for developer accounts can grant attackers unauthorized access to source code, build systems, and sensitive infrastructure. This compromise can lead to the injection of malicious code into legitimate software, impacting downstream users. Addressing this vulnerability requires robust password policies, multi-factor authentication, and regular security audits to protect the integrity of the software development process and prevent supply chain attacks. → hackernoon.com
2026-07-20 2026How agentic endpoint security shuts down IDE-based supply chain attacks intermediateAgentic endpoint security offers a new defense against IDE-based supply chain attacks. These attacks exploit vulnerabilities within integrated development environments (IDEs) to inject malicious code, compromising development workflows and software. Agentic solutions leverage AI-powered agents deployed on endpoints. These agents continuously monitor IDE activity, analyze code for suspicious patterns, and detect anomalous behavior in real-time. By proactively identifying and neutralizing threats within the IDE itself, agentic security prevents compromised code from entering the software supply chain, thereby safeguarding against widespread infections. → cybersecuritydive.com
2026-07-20 2026SleeperGem Uses Three Malicious RubyGems Packages to Target Developer Machines news 3 min readLibrary detailing the SleeperGem supply chain attack targeting Ruby developers. This attack leveraged three malicious gems: `git_credential_manager` (impersonating Microsoft's Git Credential Manager), `Dendreo`, and `fastlane-plugin-run_tests_firebase_testlab`. The gems act as loaders, fetching secondary payloads from an attacker-controlled Forgejo host, detecting and avoiding CI systems, and installing a native daemon with persistence mechanisms on developer machines, including a potential setuid root shell. → thehackernews.com
2026-07-20 2026SleeperGem: RubyGems supply chain attack targets dormant maintainer accounts intermediate 3 min readLibrary for detecting RubyGems supply chain attacks, specifically detailing the "SleeperGem" campaign. This attack involved hijacking dormant maintainer accounts for gems like `git_credential_manager`, `Dendreo`, and `fastlane-plugin-run_tests_firebase_testlab`. The malicious gem `git_credential_manager` downloaded binaries from a Forgejo host with SSL verification disabled and employed CI environment variable checks to target developer laptops. The attack escalated by embedding the malicious payload directly into the gem's load path, executing it upon mere `require`. → aikido.dev
2026-07-20 2026Cyber attacks expose supply chains as weakest link beginnerCyberattacks are increasingly targeting and exploiting vulnerabilities within supply chains, revealing them as the weakest link in organizational security. This trend highlights the interconnected nature of businesses, where a breach in one company can have cascading effects on its partners and customers. The article emphasizes the need for robust security measures and collaboration across supply chains to mitigate these growing threats.
2026-07-18 2026easy-day-js Supply Chain Attack Hits Mastra AI in npm news 3 min readAnalysis of the `easy-day-js` supply chain attack targeting the `@mastra` organization on npm details a multi-stage dropper involving crypto-stealing logic. Attackers hijacked an npm account to replace the legitimate `dayjs` dependency with the malicious `easy-day-js` package, which used a `postinstall` script to disable TLS verification, connect to hardcoded C2 servers, download and execute a second-stage payload from the OS temp directory, and perform self-deletion to hinder forensics. This incident highlights vulnerabilities in npm's package review process and the persistent risks of typosquatting and dependency hijacking. → ox.security
2026-07-17 2026Microsoft at Black Hat USA 2026: Defending trust in the age of AI and supply chain attacks news 7 min readTalk from Black Hat USA 2026 detailing how threat actors are targeting trusted software, services, identities, and AI systems. It highlights sessions on defending against AI and supply chain attacks, including research on ongoing npm supply chain attacks and vulnerabilities in Azure Automation for cross-tenant identity takeover. The talk also covers exploit techniques like those for Bixby and GitHub, emphasizing the need for security teams to understand and secure trust paths in an era of escalating offensive capabilities. → microsoft.com
2026-07-17 2026OWASP CVE Lite CLI Graduates to Lab Project Status news 3 min readTool, OWASP CVE Lite CLI, is a fast, open-source dependency vulnerability scanner for JavaScript and TypeScript projects that scans lockfiles locally against the OSV database. It supports npm, pnpm, Yarn, and Bun, classifies findings as direct or transitive, and generates a ranked remediation plan with actionable upgrade commands. The tool integrates into developer workflows with fast, local execution, no third-party data transmission, and CI-friendly output modes, having achieved OWASP Lab Project status. → owasp.org
2026-07-17 2026The practical checklist for defending against supply chain attacks intermediate 6 min readChecklist for defending against supply chain attacks, this practical guide offers prioritized tasks for hardening your stack. It addresses critical, high, and medium-priority areas including dependency management, access controls, CI/CD hardening, container security, developer environment lockdown, and monitoring. Specific defenses covered include enforcing package age policies, pinning pipeline dependencies to commit SHAs, treating MCP servers as third-party dependencies, guarding against prompt injection in AI-powered pipelines, and capturing audit logs for registry pushes, CI runs, and token usage, aiming to prevent breaches like those seen with Axios and Chalk. → aikido.dev
2026-07-17 2026600000 Monthly Downloads Affected: Miasma Supply Chain Attack Is Back on npm news 2 min readWriteup of the Miasma supply chain attack, a Shai-Hulud variant resurfacing on npm, impacting 600,000+ monthly downloads across 57 packages. This multi-stage dropper now bypasses "postinstall" execution by leveraging a weaponized `binding.gyp` file, stealing GitHub tokens, npm tokens, cloud credentials, and local environment information. The attack signature "Miasma – The Spreading Blight" was observed in over 118 infected GitHub repositories. → ox.security
2026-07-17 2026Injective npm Supply Chain Attack: 18 Packages Backdoored to Steal Crypto Wallet Keys news 5 min readLibrary for detecting an Injective npm supply chain attack where 18 packages, including `@injectivelabs/sdk-ts`, were backdoored. The malicious code, disguised as analytics, exfiltrated crypto wallet recovery phrases and private keys by sending them to an attacker-controlled server via a base64-encoded string in the `X-Request-Id` header during key derivation, specifically `PrivateKey.fromMnemonic()` and `PrivateKey.fromHex()`. → stepsecurity.io
2026-07-16 2026Unpacking the AsyncAPI npm supply chain compromise and import-time payload delivery intermediate 11 min readAnalysis of the @asyncapi npm supply chain compromise details a multi-stage attack exploiting a vulnerable GitHub Actions workflow to inject malicious loaders into five package versions. This campaign bypassed traditional `npm install --ignore-scripts` mitigations by executing its payload at module import time, leading to the download and execution of a Miasma modular runtime with C2, persistence, and fallback channels. Microsoft Defender Antivirus detects related artifacts as Trojan:JS/MiasmStealer.SC and Trojan:Script/Supychain.A. → microsoft.com
2026-07-16 2026Compromised AsyncAPI npm Packages Deliver Multi-Stage Botnet Malware intermediate 4 min readLibrary for detecting multi-stage botnet malware distributed through four compromised @asyncapi npm packages, including `@asyncapi/generator-helpers`, `@asyncapi/generator-components`, `@asyncapi/generator`, and `@asyncapi/specs`. The malware, tracked by Microsoft as MiasmStealer and Supychain, leverages a hidden JavaScript implant that executes upon module load, downloading an encrypted second-stage payload named Miasma from IPFS. This framework supports multiple C2 channels, including HTTP, Nostr relay, and IPFS, and features persistence mechanisms and a dead man's switch. The compromise originated from a misconfigured GitHub Actions workflow (`pull_request_target`) in the `asyncapi/generator` repository. → thehackernews.com
2026-07-15 2026M-Red-Team: AsyncAPI Supply Chain Compromise via GitHub Actions intermediate 4 min readLibrary for detecting and analyzing AsyncAPI supply chain compromises via GitHub Actions, specifically detailing the "pwn request" vulnerability class. It covers the exploitation of a misconfigured `pull_request_target` workflow, exfiltration of a privileged Personal Access Token, and the subsequent publication of malicious npm packages under the `@asyncapi` namespace. The analysis also notes connections to the Miasma malware framework and includes details on the multi-stage payload, its persistence mechanisms, and credential theft capabilities. → wiz.io
2026-07-15 2026AsyncAPI npm packages backdoored via GitHub Actions news 9 min readLibrary detailing the compromise of five @asyncapi npm packages, including @asyncapi/specs and @asyncapi/generator. The attacker exploited a GitHub Actions pull_request_target vulnerability in the asyncapi/generator repository to steal an npm publish token. This allowed the injection of an obfuscated downloader into the affected packages, which fetched an encrypted Node.js loader from IPFS, saving it as sync.js and executing it as a detached process. The payload installs a persistent implant identified as M-RED-TEAM v6.4, capable of establishing a remote shell for arbitrary command execution. → aikido.dev
2026-07-15 2026Veiled in Trust: Software Supply Chain Attacks Explained beginner 5 min readSurvey of software supply chain attacks, detailing methods like typosquatting, dependency confusion, and CI/CD compromise. It highlights how attackers exploit trust in open source packages, build pipelines, and maintainer accounts, citing examples like the SolarWinds SUNBURST backdoor, Shai-Hulud worm, and PhantomRaven. Defense strategies emphasize dependency inventory with SBOMs, malware detection before builds, pipeline hardening, version control, and least-privilege principles. → endorlabs.com
2026-07-15 2026AsyncAPI npm organization compromised 2M weekly downloads affected news 3 min readLibrary compromise analysis detailing a multi-stage supply chain attack targeting AsyncAPI npm packages, impacting millions of weekly downloads. The sophisticated malware functions as an info-stealer, crypto-stealer, and RAT, utilizing legitimate infrastructure like IPFS and BitTorrent for C2 communication and data storage. It self-duplicates across npm, PyPI, and Cargo, and employs evasion techniques like locale checks for Russian machines and VM/EDR detection. Recommended actions include revoking tokens, monitoring peer-to-peer traffic, and auditing code repositories. → ox.security
2026-07-14 2026Coordinated AsyncAPI Supply Chain Attack: Miasma RAT Delivered via Compromised CI/CD Pipelines in Two Repositories intermediate 11 min readLibrary for detecting and blocking coordinated AsyncAPI supply chain attacks. This resource details the Miasma RAT delivery via compromised CI/CD pipelines in two AsyncAPI repositories, impacting packages like `@asyncapi/generator` and `@asyncapi/specs`. It highlights how attackers exploited legitimate GitHub Actions release workflows and OIDC provenance to publish malicious npm packages, and how Harden-Runner blocked exfiltration by identifying C2 endpoints through network telemetry. → stepsecurity.io
2026-07-14 2026M-Red-Team: AsyncAPI Supply Chain Compromise via GitHub Actions news 4 min readWriteup detailing the M-Red-Team attack, a supply chain compromise targeting the AsyncAPI project. The attack exploited a GitHub Actions "pwn request" vulnerability via pull_request_target to steal a privileged Personal Access Token. This allowed the attacker to publish malicious npm packages under the @asyncapi namespace containing a multi-stage payload. The payload includes credential theft capabilities, persistence mechanisms, and command-and-control infrastructure using channels like Nostr relays and Ethereum smart contracts, exhibiting characteristics similar to the Miasma malware framework. → wiz.io
2026-07-14 2026Active Exploitation Alert: Jscrambler npm Packages Compromised in Coordinated Supply Chain Attack (July 2026) news 5 min readLibrary that analyzes a coordinated supply chain attack on jscrambler npm packages (versions 8.14.0, 8.16.0, 8.17.0, 8.18.0, 8.20.0) and its plugins. The malicious versions injected native binaries to harvest credentials for cloud providers, cryptocurrency wallets, and AI coding assistants, targeting developer workstations and CI/CD pipelines. Detection by Socket and StepSecurity led to rapid containment by Jscrambler. → rescana.com
2026-07-14 2026The AI Supply Chain Is Your Latest Unguarded Attack Surface beginner 7 min readLibrary for securing AI supply chains, addressing risks across four layers: third-party model APIs, open-source repositories (mentioning pickle file serialization, typosquatting, and malicious LoRA adapters), orchestration frameworks (highlighting prompt injection and RAG poisoning), and infrastructure (including GPU, hyperscaler, and physical hardware concerns). Controls involve vendor assessment, internal model registries, zero trust principles for orchestration, and geographic distribution for infrastructure. → bankinfosecurity.com
2026-07-13 2026Prompt Injection Model Poisoning and AI Supply Chain Attacks Explained beginner 6 min readLibrary for understanding prompt injection, model poisoning, and AI supply chain attacks. This resource details how attackers manipulate AI instructions, corrupt training data to alter model behavior, and exploit third-party AI components like open-source models and plugins. It highlights the new attack surfaces AI introduces and explains why traditional security tools struggle to detect these threats, which often bypass conventional malware and exploit signatures.
2026-07-13 2026Two npm attacks in four days show crypto's weak point is the supply chain news 3 min readLibrary for securing JavaScript supply chains, addressing recent npm attacks like those on `@injectivelabs/sdk-ts` and Jscrambler. These incidents highlight vulnerabilities where malicious code is executed at runtime, bypassing `--ignore-scripts`, and exfiltrates sensitive data like wallet mnemonics and cloud credentials via disguised HTTP requests. The attacks exploit compromised GitHub accounts and stolen publishing tokens, demonstrating a critical need for defenses against supply chain compromise beyond traditional smart contract audits. → startupfortune.com
2026-07-13 2026What CISA Got Right After Its GitHub Leak: Lessons Every Organization Should Copy beginner 3 min read SecretsReference detailing lessons learned from CISA's GitHub leak incident, advocating for continuous secrets scanning, developing dedicated leak-response playbooks, simplifying reporting channels, strengthening development guardrails, and testing credential rotation. It highlights the importance of treating external reports seriously and provides practical steps for security teams to implement, drawing from CISA's experience with exposed developer secrets and simplifying relations with security researchers. → blog.gitguardian.com
2026-07-12 2026Ghostcommit: Multimodal Prompt Injection Attack Exposes AI Code Review Tools to Supply Chain Risks advanced 5 min readLibrary detailing Ghostcommit, a multimodal prompt injection attack that embeds malicious instructions within image files to bypass AI code review tools like CodeRabbit and Bugbot, enabling secret exfiltration and repository manipulation by exploiting blind spots in current AI agent workflows and supply chain dependencies. → rescana.com
2026-07-12 2026Compromised jscrambler 8.14.0 npm Release Runs Hidden Platform-Specific Binary During Install news 6 min readWriteup on a compromised jscrambler npm package (version 8.14.0 and others like 8.16.0, 8.17.0, 8.18.0, 8.20.0) reveals an infostealer that runs a platform-specific native binary during installation. This payload targets cloud credentials (AWS, Azure, Google Cloud), cryptocurrency wallets (MetaMask, Phantom, Exodus), password managers (Bitwarden), browser secrets, and AI coding tool configurations. The malware employs eBPF on Linux and persistence mechanisms on Windows and macOS, communicating with C2 servers at 37.27.122[.]124 and 57.128.246[.]79. → thehackernews.com
2026-07-10 2026Injective software package hit by malicious supply chain attack news 1 min readLibrary for building Injective applications, compromised via a malicious supply chain attack on the `@injectivelabs/sdk-ts` package (v1.20.21) published to npm. Attackers gained access to a contributor's GitHub account to push malicious commits and, under the guise of telemetry, uploaded a backdoor that stole developers' private keys and mnemonic seed phrases when using `fromMnemonic` or `fromHex` wallet generation functions. The attack spread through transitive dependencies in 17 additional Injective packages.
2026-07-10 2026Turning software supply chain security into a daily habit beginnerGuide on operationalizing software supply chain risk, arguing for daily use of SBOMs beyond compliance for vulnerability triage, vendor access reviews, identity monitoring, and incident response. It draws on Group-IB’s High-Tech Crime Trend Report 2026 to illustrate how supply chain attacks link phishing, ransomware, and data breaches through inherited trust. The guide details prioritizing exposed systems, defining compromise windows, containing stolen credentials, and vendor risk scoring, highlighting AI's acceleration of attack timelines. → helpnetsecurity.com
2026-07-10 2026Xsnow "protestware" in Debian news 4 min readWriteup detailing the "protestware" controversy surrounding the Xsnow application in Debian. The entry discusses how Xsnow's maintainer included a feature that displayed Ukrainian flags when the application's language was set to Russian. This triggered a debate on the Debian development list regarding potential violations of the Debian Free Software Guidelines (DFSG), specifically concerning discrimination. While Xsnow itself was deemed DFSG-compliant, the discussion highlighted concerns about software exhibiting deceptive behavior based on user settings.
2026-07-10 2026Symlinks Are Still Scary (And Yes, You Can Commit Them to Git) beginner 12 min read AIReference detailing symlink attacks, where a file's content is a path to another location, allowing malicious repositories to trick tools into reading or writing sensitive files. This technique, exemplified by CVE-2024-32002 and CWE-61, bypasses security by exploiting how programs handle file paths without proper resolution, leading to potential remote code execution when combined with Git's support for committing symlinks, as seen in attacks against AI coding assistants and archive tools. → snyk.io
2026-07-10 2026Compromised @injectivelabs/sdk-ts exfiltrates wallet keys through fake telemetry news 5 min read SecretsWriteup detailing a malicious release of `@injectivelabs/sdk-ts` version 1.20.21, which exfiltrated wallet mnemonics and private keys by masquerading as telemetry. The compromised package subtly injected code into `PrivateKey.fromMnemonic` and `PrivateKey.fromHex` to capture sensitive data and send it to an attacker-controlled endpoint disguised as normal gRPC-web traffic. The attack also involved republishing 17 other `@injectivelabs` packages with a hard dependency on the poisoned SDK, highlighting the risks of transitive dependencies. → aikido.dev
2026-07-09 2026Active Exploitation Alert: Prompt Injection Vulnerability in GitHub Agentic Workflows Threatens Software Supply Chain Security news 5 min readAnalysis of prompt injection attacks targeting GitHub agentic workflows, affecting tools like GitHub Copilot, Google Gemini CLI, and Anthropic Claude Code. These attacks, demonstrated in campaigns like GhostAction and the NX Build System compromise, leverage CWE-1427 (Improper Neutralization of Untrusted Input for LLM Prompting) and MITRE ATT&CK T1677 (Poisoned Pipeline Execution) to steal credentials, execute arbitrary code, and modify repositories, impacting software supply chain security. → rescana.com
2026-07-09 2026Secure AI Workflows: The Identity and Access Management (IAM) Checklist beginner 3 min read AIChecklist for securing AI workflows, detailing an 8-point roadmap for implementing effective Identity and Access Management (IAM) for human-assisted AI tools like Claude Code and Cursor, and autonomous agents in CI/CD pipelines. It emphasizes granular tool-level permissions, restricted user-scoped tokens, dynamic permission validation, composite identities, safe output restrictions, and deterministic infrastructure-level IAM policies to prevent unauthorized access and maintain auditability across the software development lifecycle. → jfrog.com
2026-07-08 2026GitLost: a public GitHub issue can steer an org's Agentic Workflow into leaking private repo contents, and a one-word prefix ("Additionally") bypassed the threat-detection guardrail intermediate 4 min readLibrary detailing GitLost, a prompt injection vulnerability in GitHub's Agentic Workflows. An unauthenticated attacker can exploit GitLost by posting a crafted GitHub Issue in a public repository, tricking the AI agent into leaking private repository contents. The vulnerability arises from treating user-controlled content as trusted instruction input, bypassing guardrails like the "Additionally" keyword, allowing unauthorized access to files such as README.md from private repositories within the same organization.
2026-07-04 2026I found North Korean (DPRK) malware hiding in my tailwind.config.js news 13 min readLibrary for detecting North Korean (DPRK) malware injected into Node.js projects, specifically found in `tailwind.config.js` files. This malware uses obfuscated code and attempts to exfiltrate data to `api.trongrid.io`. The library highlights the risks of compromised build tools and starter templates, emphasizing the need for thorough inspection of project configuration files. → infosecwriteups.com
2026-07-02 2026This Report from Gartner Defines the Software Supply Chain Security Market news 4 min readLibrary providing comprehensive software supply chain security, including Spectra Assure for enterprises and Spectra Assure Community for open-source package analysis. This solution addresses market needs highlighted by Gartner's recognition and evolved from foundational work addressing attacks like SolarWinds, offering deep binary analysis, automated risk assessment, SBOM generation, and CI/CD integration for vendors like Azure DevOps, Jenkins, and GitLab CI. → reversinglabs.com
2026-07-01 2026NetRise brings managed software supply chain risk management to federal partners news 1 min readLibrary for managed software supply chain risk management, targeting federal integrators and MSPs. It combines binary analysis with NetRise Provenance to provide context on software origin, maintainers, repository health, and downstream exposure. The offering helps validate SBOMs, build software inventories, identify cryptographic algorithms and libraries, and supports federal workflows like RMF, ATO, and continuous monitoring. It addresses federal pressure for better software visibility due to risks from vendors, open source, and third-party products, and supports initiatives around vulnerability remediation and AI security. → msspalert.com
2026-07-01 2026And another one. GitHub ships break-glass credential revocation news 5 min readLibrary for bulk credential revocation in GitHub Enterprise, allowing owners to instantly cut off compromised Personal Access Tokens, SSH keys, and OAuth tokens across an organization. This "break-glass" feature addresses the challenges of incomplete credential rotations, as seen in recent attacks on Trivy and Microsoft's own repositories, by providing a single action to revoke all credentials, preventing attackers from leveraging lingering access. The library also emphasizes pinning GitHub Actions to full commit SHAs instead of tags to mitigate supply chain risks. → aikido.dev
2026-07-01 2026Phantom Squatting: AI-Hallucinated Domains as a Software Supply Chain Vector advanced 22 min read AIAnalysis of "Phantom Squatting" details how large language models hallucinate web domains, which adversaries then register to intercept traffic from AI systems, posing a significant software supply chain risk. Researchers identified over 13,000 confirmed malicious URLs and approximately 250,000 unregistered hallucinated domains. One real-world case involved an attacker using an AI coding assistant to build a phishing kit targeting a domain predicted to be a high-risk hallucination target. This technique bypasses traditional defenses by leveraging zero-reputation domains generated by trusted AI outputs. → unit42.paloaltonetworks.com
2026-07-01 2026Phantom Squatting: AI-Hallucinated Domains as a Software Supply Chain Vector advanced 22 min readLibrary of resources detailing "phantom squatting," a software supply chain vulnerability where adversaries register AI-hallucinated domains to intercept traffic from LLMs used in development. The research highlights how tools like the Montana Empire phishing kit leverage this vector, bypassing traditional security measures by exploiting the zero-reputation nature of newly registered, AI-generated domains. → unit42.paloaltonetworks.com
2026-06-30 2026Decades-Old Bash Tricks Expose AI Coding Agents to Supply Chain Attacks intermediate 4 min readLibrary that prevents GuardFall vulnerabilities where Bash shell tricks, such as quote removal and $IFS spacing, are used to inject malicious instructions into AI coding agents. The research tested eleven popular open-source agents, including Hermes and Roo-code, finding that most are susceptible to these decades-old Bash techniques, which can lead to supply chain attacks like AWS credential exfiltration or deletion of development environments, particularly in CI pipelines. Only the Continue agent successfully blocked all tested bypass cases. → securityweek.com