socket.dev
Resources curated from this publisher and indexed across appsec.fyi topic pages. Last item added: 2026-11-19.
| Date Added | Resource | Excerpt |
|---|---|---|
| 2026-11-19 2026 | Optimizely Supply Chain Attack Distributes Malware Across Global BrandsSupply Chain | Analysis of the Optimizely Supply Chain Attack details how attackers exploited a vulnerability in Optimizely's Web Experimentation platform, injecting malicious JavaScript into global brands like BBC, CNN, and HSBC. This attack delivered cryptocurrency clippers, card skimmers, and iOS malware by compromising trusted third-party scripts. The vulnerability resided in the Project JavaScript field, allowing the execution of custom code, and was patched by Optimizely. |
| 2026-11-19 2026 | Microsoft’s agent-framework PyPI package Compromised with Credential StealerAIPythonSupply Chain | Library that, when compromised in agent-framework versions 1.26.1 and 1.26.2, utilizes Python `.pth` startup hooks to exfiltrate Azure, GitHub Actions, and CI/CD credentials. The malicious code silently harvests environment variables, cloud identity tokens, and configuration files, then transmits them to a webhook.site endpoint. |
| 2026-11-10 2026 | Malicious bee-js npm Release and Swarm Desktop Releases Deliver SleepyDuck Ethereum C2 BackdoorSupply Chain | Library for analyzing the SleepyDuck/EtherDuck C2 backdoor delivered via malicious @ethersphere/bee-js npm and Swarm Desktop releases. This entry details the compromise of Ethersphere’s release pipeline, the loader's functionality, and its connection to previous Open VSX campaigns, noting the reuse of Ethereum C2 infrastructure identified by Pluto Security and safeDep. |
| 2026-11-09 2026 | Shai-Hulud Descendant Surfaces in Malicious Ruby Gem That Steals Credentials and Poisons AI ToolsSecretsSupply Chain | Library utilizing a malicious Ruby gem, `strutil-core` version 1.0.1, which installs a credential-stealing worm and poisons AI tools. This gem, a descendant of the Shai-Hulud toolkit, executes a Python backdoor, attempts to self-propagate across various platforms like RubyGems, npm, and PyPI, and can wipe files if a stolen GitHub token is revoked. The payload, obfuscated and encrypted, collects sensitive data including cloud, CI, AI coding tool, and wallet credentials. |
| 2026-11-07 2026 | Hardening GitHub Actions Against Outside ThreatsSupply Chain | Library for securing GitHub Actions against supply chain attacks, focusing on outside threats. It details vulnerabilities exploited through malicious pull requests, credential theft, dependency risks, and release pipelines, referencing incidents like tj-actions/changed-files (CVE-2025-30066), reviewdog/action-setup, and trivy-action. The library advocates for practices like using workflow lockfiles with tools like `gh actions-lock`, pinning reusable workflows by SHA, and leveraging organization policies to enforce security. It also discusses checks like `zizmor`'s impostor-commit rule to prevent malicious code injection via forks or unverified commits. |
| 2026-11-07 2026 | GitHub to Block pull_request_target Workflows by Default Starting December 2Supply Chain | Reference detailing GitHub's upcoming default blocking of `pull_request_target` workflows in public repositories starting December 2, 2026. This security enhancement aims to mitigate CI/CD vulnerabilities exploited in supply chain incidents involving Nx, PostHog, and TanStack. The change restricts workflows triggered by `pull_request_target` unless an explicit Actions event policy allows them, impacting legitimate automation tasks like labeling pull requests and managing metadata. GitHub is conducting brownout tests in November to allow maintainers to identify and configure exceptions for their workflows. |