For years, many organizations have built their defenses on one assumption: software that comes from an official vendor, repository, or marketplace must be safe. Between early and mid November 2026, that assumption was tested again. A string of incidents shows that attackers no longer always go after their targets directly. They get in upstream, through developer accounts, release pipelines, open source packages, extensions, and even hardware from resellers, and then let a trusted distribution channel carry the attack to many victims at once. The focus of cybersecurity is therefore shifting from guarding the perimeter to Supply Chain Security: making sure every component that enters our environment, from code, packages, and updates to third-party credentials, can be trusted and verified.
1. Anatomy of an Attack: Getting In Through Trusted Channels
The latest incidents share the same pattern: attackers abuse the trust already attached to a source instead of looking for a flaw in the victim’s own systems.- Release pipelines and CI/CD automation: Attackers used the Ethersphere project’s own release automation to publish malicious versions of bee-js 13.3.0 and Swarm Desktop 0.56.2, targeting wallet keys and installing backdoors. Separately, Aikido Security reported that stolen credentials for 4,837 GitHub accounts were used to plant a CI secret stealer in at least 1,806 repositories.
- Marketplaces and developer extensions: Cursor disclosed that attackers copied data from a shared storage bucket using an access key issued to Fireworks AI that had leaked, after a trojanized Claude Code extension had been distributed through Cursor’s marketplace.
- Installers and popular packages: Binance said its record USD 6.43 billion theft began with a trojanized Homebrew installer downloaded by one of its engineers. In the same period, environments that ran litellm 1.107.0 or Rank Math PRO v3.0.123 within the documented windows were advised to be treated as fully compromised, with mandatory credential rotation.
- Hardware and resellers: Trezor confirmed that three Trezor Safe 5 wallets bought from the reseller CryptoBilis contained a hidden circuit board that could capture recovery phrases and send them to attacker servers.
2. Credentials and Third-Party Access: The Keys Attackers Want Most
Almost every incident above comes down to one thing: credentials. Wiz reported that an attacker used credentials for an AWS account that the Qubole platform uses to access customer accounts, stealing secrets and data between October 14 and 26. In other words, an organization’s security now also depends on how carefully its vendors and partners manage their own access.- Overly broad vendor access: Keys or access roles granted to third parties are often rarely reviewed, not limited in scope, and have no expiry date.
- Risk in AI models: Microsoft researchers showed that an AI model can be given a hidden backdoor by editing fewer than 10 rarely used neurons, without retraining. Microsoft said it has not seen threat actors use the technique, but it underlines that AI models and tools are part of the supply chain too.
3. Strengthening Strategy: Building a Verifiable Supply Chain
To deal with this threat, organizations can focus on three main operational pillars:A. Dependency Inventory and Version Control Organizations cannot protect components they do not know about. Build a software bill of materials (SBOM), pin dependency versions, and avoid pushing updates to production on the same day they are released. A short delay gives the security community time to find malicious packages before they reach core systems.
B. Secrets Management and Least Privilege Keep credentials in a secret manager, not in code or CI configuration. Limit developer and vendor access to what is needed, enforce MFA on repository accounts, and have a credential rotation procedure that can be run quickly when a package or vendor is reported as compromised.
C. Integrity Verification and Isolated Build Environments Separate build environments from the core network, verify digital signatures and checksums of installers before installing them, and download tools only from official sources. For hardware, buy only through official distribution channels and check seals and authenticity before use.