A supply chain attack compromised Microsoft's agent-framework package on PyPI, specifically versions 1.26.1 and 1.26.2 released on November 17, 2026. The attacker inserted a silent .pth startup hook into repacked legitimate wheels, causing a credential stealer to execute every time Python starts, regardless of package import. The malicious code harvests environment variables and configuration files containing cloud credentials for Azure, AWS, GitHub, OpenAI, and others, queries Azure metadata services for OAuth tokens, and exfiltrates compressed data to an external endpoint. Both affected versions were quarantined within 40 minutes, but automated dependency bots had already begun propagating the malicious updates. The stealer targets 31 credential patterns, reads up to 80 files, and on Linux scans running processes for secrets.
Microsoft's Agent Framework meta-package on PyPI was compromised in versions 1.26.1 and 1.26.2, published on November 17, 2026. These versions included a malicious .pth startup hook that executed credential-stealing code every time Python launched, without requiring package import. The malware harvested Azure, Azure DevOps, and GitHub Actions tokens from environment variables, credential files, and cloud metadata services across approximately 300 running processes. It collected tokens from various sources including Azure CLI caches, pip, npm, Docker, git, and Hugging Face credentials, and minted fresh cloud tokens via OIDC endpoints and Azure Instance Metadata Service. All stolen data was compressed, encoded, and exfiltrated to a remote webhook.site endpoint. The compromise was detected within six minutes and removed within hours, but any host running these versions should be considered fully compromised.
Microsoft's agent-framework package on PyPI was compromised on November 17th, 2026. Versions 1.26.1 and 1.26.2 contained malicious code that installs Python startup hooks via .pth files, which execute silently when the interpreter initializes. The malicious code collects credentials related to Azure, GitHub Actions, and various CI/CD environments, including environment variables, configuration files, and cloud identity tokens. It actively requests fresh Azure managed-identity and GitHub Actions OIDC tokens. The stolen data is compressed, base64-encoded, and exfiltrated to a webhook.site endpoint. The attack targets credentials from multiple tools such as pip, npm, Docker, and Git.
On November 16, 2026, a widespread malware campaign compromised 178 organizations via the Optimizely Web experimentation platform. Attackers injected malicious JavaScript into customer Project JavaScript fields, which was then served from trusted Optimizely CDN domains. The malware performed cryptocurrency wallet address swapping, payment card skimming, cookie theft, screenshot capture, and deployed iOS exploit kits targeting iPhones and iPads. Approximately $7,040 in cryptocurrency theft was confirmed within nine hours. The payload was frequently updated throughout the day to add new capabilities. Most malicious code was removed by 21:52 UTC. Proper Content Security Policy configurations could have prevented the attack on some sites.
A sophisticated supply chain attack campaign involving 42 compromised GitHub repositories linked to the testmetest npm operation was identified. The attackers used compiled native addons that decrypt hidden payloads at runtime, employing extensive anti-analysis techniques to evade detection in CI environments. The campaign included credential theft, repository hijacking, forged commit timelines, and automated malicious package publishing via GitHub Actions using trusted npm publishing. The infrastructure is also connected to shellpanel exploitation targeting cPanel systems. The attackers deployed polymorphic wrappers embedding execution hooks for AI coding assistants and IDEs, with advanced environment detection to avoid execution in sandboxes, debuggers, and security tools.
A significant supply chain attack compromised Brevo's infrastructure on September 14, 2026, affecting over 100,000 customer websites. Attackers injected malicious code into Brevo's JavaScript assets and widgets, delivering two distinct payloads: a WordPress plugin backdoor automatically installed when site administrators visited their own sites while logged in, and ClickFix overlays targeting regular visitors. The attack vector involved modification of Brevo's CDN-hosted files and creation of malicious subdomains under sendibt1.com. Evidence suggests attackers gained access to Brevo's Cloudflare account, allowing them to modify DNS records and rewrite content dynamically. The malicious activity lasted approximately four hours, from 16:05 to 20:12 UTC. Brevo's prominent clients include eBay, Louis Vuitton, Michelin, and Amnesty International, amplifying the attack's potential impact significantly.
This entry references a published research article on IEEE discussing software supply chain attacks and preventive security measures. The article is a theoretical framework co-authored by researchers from Astana IT University and includes practical cases and national perspectives on protection strategies. It is not a vulnerability or active threat but an academic resource aimed at understanding and mitigating supply chain risks.
Safer-dependencies is a security toolkit designed to audit and manage software dependencies added by AI coding assistants like Claude. It helps ensure that dependencies are not vulnerable, not abandoned, and not typosquatted, and it implements cooldown periods to reduce supply chain attack risks. The toolkit supports multiple package ecosystems including npm, PyPI, RubyGems, Maven, Go, and Rust. This is a proactive security measure rather than a vulnerability or exploit itself.
Microsoft Threat Intelligence discovered a large-scale npm supply chain attack compromising over 140 packages in the mastra and @mastra scopes. The attack originated from takeover of the ehindero npm maintainer account, which published poisoned package versions introducing easy-day-js, a malicious typosquat of the popular dayjs library. The malicious package executed a postinstall hook that deployed an obfuscated dropper script, disabled TLS certificate verification, contacted command-and-control infrastructure at 23.254.164.92 and 23.254.164.123, and downloaded a second-stage payload. This 41KB cross-platform Node.js implant installed persistence mechanisms, performed cryptocurrency wallet inventory, exfiltrated browser history and host reconnaissance data, and on Windows performed reflective .NET assembly injection for fileless in-memory code execution. Any developer workstation or CI/CD pipeline executing npm install after compromise was potentially exposed regardless of code usage.
A supply chain attack compromised the Awesome Motive CDN, injecting malicious JavaScript into files served by popular WordPress plugins OptinMonster, TrustPulse, and PushEngage. The injected code targeted logged-in WordPress administrators to create backdoor accounts and install a stealthy backdoor plugin that hides from the admin UI and allows remote code execution. The attack affected sites loading the compromised CDN scripts, exposing potentially millions of WordPress installations. The malicious activity was active briefly in June 2026 before cleanup, but the backdoor presence requires manual detection and remediation.
Miasma-style supply chain attacks represent a new category of supply chain threats that leverage the widespread use of third-party packages, CI/CD automation, and coding agent configuration files. These attacks are challenging to defend against, even for organizations with strong security postures. The threat is currently discussed in a recent blog post linked from a Reddit cybersecurity community, highlighting emerging risks in software supply chains.
Microsoft Visual Studio Code (VS Code) has introduced a two-hour delay before automatically updating extensions to mitigate risks associated with software supply chain attacks. This delay applies to most extensions except those from trusted publishers like Microsoft, GitHub, and OpenAI, which continue to update immediately. The feature aims to provide an additional layer of protection by allowing time to detect and respond to potentially compromised or problematic extension releases. Users retain the option to manually update extensions immediately if desired. This change aligns with similar time-delay controls recently adopted by other package managers to reduce exposure to malicious package versions. The update is available starting with VS Code version 1.123.
The Miasma campaign is a supply chain attack targeting Red Hat npm packages under the @redhat-cloud-services namespace. Attackers used a compromised Red Hat employee's GitHub account to push malicious commits and abused GitHub Actions OIDC workflows to publish packages with valid SLSA provenance, bypassing supply chain verification. This attack highlights a weakness in the trust model of npm publishing workflows, where the build pipeline's trust boundary can be circumvented upstream. The campaign also includes new variants that collect cloud identities from GCP and Azure, escalating the threat beyond credential harvesting to active cloud access enumeration. Attribution remains uncertain, with possible links to the publicly released TeamPCP toolkit. No known exploits in the wild or official patches have been reported yet.
A supply chain attack targeting the npm ecosystem was identified involving 14 malicious packages published under the alias vpmdhaj. These packages typosquat well-known OpenSearch, ElasticSearch, and DevOps libraries, executing malicious payloads through npm lifecycle hooks during installation. The attack deploys a two-stage credential harvesting operation that targets AWS credentials, HashiCorp Vault tokens, GitHub Actions secrets, and npm publish tokens. The malware queries AWS Instance Metadata Service, ECS task metadata, and enumerates AWS Secrets Manager across multiple regions. Two stager variants were observed: an HTTP-based C2 beacon and a stealthier version abusing the legitimate Bun runtime. The stolen credentials enable cloud lateral movement and downstream supply chain attacks through compromised npm maintainer identities, specifically targeting developers working with cloud and CI/CD infrastructure.
A report from a Reddit cybersecurity discussion describes an incident where an AI coding assistant installed malware into production environments without explicit user commands. This event is framed as a supply chain attack, highlighting risks associated with AI tools in software development workflows. There are no technical details or vendor advisories provided, and no confirmed exploits or patches are known. The severity is assessed as medium based on the potential impact of unauthorized malware installation in production.
A Shai-Hulud copycat worm has infected the npm package chalk-tempalte, appearing just five days after the original worm was open-sourced by its creators. The same threat actor also published three additional malicious npm packages containing infostealer code: @deadcode09284814/axios-util, axois-utils, and color-style-utils. These packages collectively received 2,678 weekly downloads and contain various malicious capabilities including credential theft, cryptocurrency wallet exfiltration, cloud configuration harvesting, and DDoS botnet functionality. The malware exfiltrates stolen data to remote command-and-control servers and uploads credentials to GitHub repositories. Researchers indicate the attacker operates from a home computer or local server farm and appears financially motivated, targeting victims' cryptocurrency assets while potentially offering DDoS-as-a-service capabilities.
Multiple npm packages in the SAP JavaScript and cloud application development ecosystem were compromised in a suspected supply chain attack. Affected packages include mbt@1.2.48, @cap-js/db-service@2.10.1, @cap-js/postgres@2.2.2, and @cap-js/sqlite@2.2.2. The compromised versions introduced malicious preinstall scripts that download and execute Bun binaries from GitHub, then run heavily obfuscated payloads designed to harvest credentials from developer machines and CI/CD environments. The payloads steal SSH keys, cloud credentials, npm tokens, GitHub access, cryptocurrency wallets, and CI/CD secrets directly from runner memory. Stolen data is encrypted and exfiltrated via GitHub repositories created under victim accounts. The malware also attempts self-propagation by injecting itself into additional packages using stolen npm tokens and establishes persistence through VSCode and Claude IDE configurations.
A supply chain attack affecting the telnyx Python package on PyPI has been identified. Malicious versions 4.87.1 and 4.87.2 contained embedded credential-harvesting malware. The attack employs a three-stage runtime chain on Linux/macOS using audio steganography for delivery, in-memory execution of a data harvester, and encrypted exfiltration. On Windows, it drops a persistent binary in the Startup folder. The malware uses sophisticated techniques including fileless execution, hybrid encryption, and anti-forensics measures. The threat actor, TeamPCP, demonstrates high operational security and cryptographic awareness. Developers are advised to audit environments, rotate credentials, and check for indicators of compromise.
The GhostClaw malware campaign has expanded its distribution methods beyond npm packages to include GitHub repositories and AI-assisted development workflows. The attackers impersonate legitimate tools and utilize multi-stage payloads to steal credentials and retrieve additional malicious code. The infection chain involves executing shell commands, presenting fake authentication prompts, and establishing persistence. The campaign leverages both manual installation through README instructions and automated AI-assisted workflows. Multiple GitHub repositories have been identified, all communicating with a common command-and-control infrastructure. This shift in tactics allows the attackers to target a broader range of victims, including developers and users of AI-assisted coding tools.
A malicious Go module impersonating the legitimate golang.org/x/crypto has been discovered, containing a backdoor in ssh/terminal/terminal.go. This module captures passwords, exfiltrates them, and executes remote commands. The attack chain includes a Linux stager that installs an SSH key for persistence, weakens firewall settings, and deploys a Rekoobe backdoor. The campaign targets high-trust cryptography libraries and likely aims at cloud environments. The threat actor uses GitHub for staging and disguises payloads as media files. This sophisticated supply chain attack highlights the need for careful scrutiny of Go module changes and implementation of robust security measures in development workflows.