Last updated: November 2, 2026 at 1:20 PM UTC
All 957 Vulnerability 399 Breach 144 Threat 407 Defense 7
Tag: supply-chain (144 articles)Clear

Trojanized Claude Code extension on Cursor Marketplace installed a persistent SSH backdoor on developer machines

OpenSourceMalware disclosed that Anthropic's official Claude Code extension was trojanized on the Cursor Marketplace, with a 66-line malicious loader inserted before the legitimate code in versions 2.1.312 and 2.1.313 for Windows and macOS. Anthropic's systems were not compromised; an actor used marketplace access to publish the tampered build. The backdoor adds an attacker SSH key labeled svc-telemetry to authorized_keys, tries to enable SSH and open a reverse tunnel to 134.209.82.225, and persists via scheduled task, crontab, and LaunchAgent, beaconing host details over plain HTTP. The malicious version was live about twelve hours on October 29, and Cursor says up to 5,000 users were affected.

Check
Identify machines that installed or auto-updated the Claude Code extension 2.1.312 or 2.1.313 from the Cursor Marketplace, then isolate them and preserve evidence.
Affected
Developers who got the trojanized extension from the Cursor Marketplace had an attacker SSH key and persistence written, even when the reverse tunnel failed without admin rights.
Fix
Remove the svc-telemetry SSH key and persistence entries, update to 2.1.314 from a trusted marketplace, rotate credentials, and note uninstalling alone leaves the artifacts behind.

Hijacked DebugBear monitoring script drains about 2.7 million dollars from Polymarket trader wallets

Hudson Rock and Ohey reported that attackers hijacked DebugBear, a real user monitoring vendor whose page-speed script Polymarket loaded, by compromising its DNS through the domain registrar rather than breaching DebugBear itself. A malicious server answered for DebugBear's addresses and served code that reused a signed-in trader's session to read stored trading API keys and move positions to the attacker, selling at worsening prices for email-login accounts. Polymarket says 726 wallets were affected and about 2.64 million dollars in POL reached the attacker within an hour, and it is returning 3.9 million dollars in total. No keys or seed phrases were exfiltrated.

Check
Inventory third-party scripts on pages that handle signing or trading, pin them with Subresource Integrity, and remove any not strictly needed.
Affected
Sites loading third-party scripts on authenticated trading or signing pages can have those scripts swapped via vendor DNS compromise to hijack sessions and move funds.
Fix
Enforce a strict content security policy and Subresource Integrity, pin and sandbox third-party scripts, and have users reject unexpected signing requests.

Brotli decoder memory corruption flaw exposes Node.js, Bun, Python, and many other programs to code execution

OpenAI's Codex Security team reported CVE-2026-111497, a memory corruption flaw in Google's Brotli decoder that Google rates 9.2, where crafted compressed data overwrites past a buffer and can crash, leak memory, or run attacker code. Because the vulnerable C code is bundled widely, every program shipping it inherits the bug, including Node.js, Bun, .NET, Envoy, Istio, Python Brotli bindings, the Ruby gem, and others, with FFmpeg, ClickHouse, and Apache Arrow also affected. Each project needs its own update, such as Node.js 24.22.1 or Bun 1.4.4. Imperva demonstrated code execution on Node.js 24, calling it Node2Shell, but no in-the-wild exploitation is reported.

Check
Inventory software that decodes Brotli, including Node.js, Bun, .NET, Envoy, Istio, and Python bindings, and apply each project's fixed version.
Affected
Programs bundling the vulnerable Brotli decoder can be crashed or driven to code execution by crafted compressed data, regardless of the application's own code.
Fix
Update every affected runtime and library to its patched release, prioritize internet-facing services that accept Brotli-compressed input, and track fixes for FFmpeg and others still pending.

Gheist campaign uses stolen GitHub tokens to leak private repository secrets through Actions logs

Wiz detailed Gheist, an automated campaign that uses stolen GitHub tokens to push a sync-check.yml workflow to a short-lived ci-sync branch, then reads the job's secrets from the run log. The workflow base32-encodes every secret the job can access, defeating GitHub's log masking, downloads the log through the API, and deletes the run seconds later, so nothing leaves through an attacker server. Since September 15, Wiz recovered more than 13,500 planted branches across more than 850 compromised accounts, succeeding in private repositories and GitHub Enterprise, where GitHub's hold on suspicious runs does not apply. Rotate every reachable secret, since deleting branches does not undo exposure.

Check
Hunt for ci-sync branches containing only a sync-check.yml workflow and runs deleted shortly after finishing, and rotate every secret those repositories could access.
Affected
Private GitHub repositories and Enterprise servers reachable with a stolen token can have all their accessible secrets leaked through a planted workflow's run logs.
Fix
Rotate repository, organization, and environment secrets, revoke the tokens that pushed commits, prefer short-lived fine-grained tokens, and require reviewers on environments holding production secrets.

Planted instructions file tries to trick AI coding agents into installing malicious npm package

Forever Security caught an attempt on a customer's machine to subvert an AI coding agent through a planted instructions file. Coding agents read AGENTS.md or CLAUDE.md files in a folder and follow them, and a web page can drop such a file into Downloads without a click. The disguised file told OpenAI Codex to register a server in its global config and install the npm package function-color, part of the MALFEX campaign, which pulls a Windows payload. Against Claude Code, a CLAUDE.md tried to set ANTHROPIC_BASE_URL to an attacker server to leak the login token. Researchers say there is nothing for vendors to patch.

Check
Do not run coding agents in the Downloads folder, and read any AGENTS.md or CLAUDE.md you did not write before letting an agent act on it.
Affected
Developers whose coding agent reads an attacker-planted instructions file can have it install malicious npm packages or redirect its base URL to leak login tokens.
Fix
Keep agent approval prompts and sandboxes on, inspect config files like the Codex config and project settings for unexpected changes, and rotate tokens if a planted file is found.

LiteLLM 1.107.0 compromised in supply chain attack delivering credential stealer and GitHub-controlled backdoor

Researchers at SafeDep, Socket, StepSecurity, and Upwind reported that LiteLLM version 1.107.0, a popular Python AI gateway, was published with malware through compromised GitHub CLI OAuth tokens belonging to three engineers. A cook.pth file runs a payload whenever the Python interpreter starts, even before LiteLLM is imported. The first stage, calling itself privcollect, harvests cloud tokens, developer credentials, private keys, AI tooling credential files, browser data, environment variables, and the proxy's saved keys and model config, exfiltrating over HTTP to litellm[.]dev/healthcheck. A second payload is a backdoor that fetches and runs further commands. The PyPI package and Docker images were pulled, and users should pin to 1.106.2.

Check
Check whether LiteLLM 1.107.0 was installed from PyPI or Docker, and if so revoke and replace all reachable credentials from a clean machine, then pin to 1.106.2.
Affected
Systems that installed LiteLLM 1.107.0 ran a credential stealer and backdoor on Python startup, exposing cloud tokens, keys, browser data, and the LiteLLM proxy's saved secrets.
Fix
Pin LiteLLM to 1.106.2 by digest, rotate every exposed credential, remove the cook.pth persistence, and block outbound traffic to the litellm.dev healthcheck exfiltration endpoint.

Attackers abuse stolen UpdraftCentral keys to install backdoor plugins on connected WordPress sites

TeamUpdraft disclosed that attackers breached its website over the October 17 weekend and reached its customer database, obtaining names, emails, hashed passwords, 2FA settings, and the UpdraftCentral connection keys that let them push backdoor plugins to connected WordPress sites. UpdraftPlus, a backup plugin with over four million installs, ships an UpdraftCentral client in every copy. Patchstack saw signed plugin.upload_plugin commands over an 18-hour window and 99 backdoor plugin names, and one backdoor creates a persistent data-ops43 editor account that survives plugin removal. Fixes are in UpdraftPlus 1.26.13 and 2.26.13, which disconnect pre-incident UpdraftCentral connections. Site owners should rotate keys and hunt for rogue accounts.

Check
Update UpdraftPlus to 1.26.13 or 2.26.13, delete the UpdraftCentral connection key, and check WordPress sites for unknown admin or editor accounts and plugins.
Affected
WordPress sites connected to cloud UpdraftCentral could receive attacker-pushed backdoor plugins and a persistent data-ops43 account that survives plugin removal and normal login unless 2FA blocks it.
Fix
Apply the fixed UpdraftPlus release, rotate UpdraftCentral and storage keys, remove rogue accounts and plugins including must-use plugins, and restore from a pre-October-17 backup if needed.

Attackers backdoor five OVHcloud CLI releases on GitHub to steal developer secrets from disk

OVHcloud disclosed that five releases of its open-source command-line tool, versions 0.11.0 through 0.15.0, were backdoored on GitHub to steal secrets from disk. An attacker who had controlled a developer's GitHub account for more than half a year modified the existing releases because GitHub release immutability was disabled, uploading locally built malware without touching the CI/CD pipeline, and planted a hidden preinstall.js loader. OpenSourceMalware linked it to the GlassWorm campaign. The malicious builds covered macOS, Linux, and Windows and were live from 14:47 to 16:21 UTC on October 19. Source builds and Docker images were unaffected, and users should revoke secrets.

Check
Identify machines that ran OVHcloud CLI versions 0.11.0 through 0.15.0, remove or update the binary, clean the systems, and revoke all secrets they could reach.
Affected
Developers who installed the backdoored OVHcloud CLI releases on macOS, Linux, or Windows had secrets stolen from disk by locally built malware uploaded to GitHub.
Fix
Update to a clean OVHcloud CLI release, rotate all exposed secrets, enable GitHub release immutability on your own repositories, and inspect hosts for the preinstall.js loader.

Compromised ConnectWise Cloud Backup credential lets attackers sign in to 173 Microsoft 365 tenants

Huntress observed attackers abusing a compromised Microsoft 365 OAuth credential for ConnectWise Cloud Backup, formerly SkyKick, to sign in to 173 partner and customer tenants. The credential works against every tenant the app is consented in, letting attackers obtain Microsoft Graph tokens and reach mailboxes, files, and directory data. In at least one tenant, a ConnectWise app added itself to the Global Administrator role and created new client secrets. Token acquisition came from a single IP on October 15, moving through tenants in sorted order. ConnectWise closed Cloud Backup access until all credentials are reset, and issued tokens stay valid for up to 90 minutes.

Check
If you use ConnectWise Cloud Backup, keep the application disabled until credentials are reset, enable Microsoft Graph activity logs, and audit for credentials added since October 13.
Affected
Microsoft 365 tenants that consented to the ConnectWise Cloud Backup app could be accessed with a compromised credential, exposing mailboxes, files, and directory data to attackers.
Fix
Disable the affected ConnectWise applications, review service principal sign-ins for application ID 506e08f9 and IP 144.172.64.128, revoke added secrets, and check for apps granting themselves admin roles.

npm Trusted Publishing slug-reuse flaw exposed over 1,500 packages to unauthorized takeover

Bloom Security disclosed a flaw in npm's Trusted Publishing, which binds a package to a GitHub repository and workflow. npm recorded the binding by repository slug rather than GitHub's permanent numeric IDs, so once a bound repository or owner was renamed, transferred, or deleted, an attacker could claim the freed slug, add a matching workflow, and receive a publish credential, even forging a valid provenance attestation. Bloom counted more than 1,500 exposed packages with over 10 million total downloads. GitHub, notified in June through HackerOne, shipped a fix in October so unvalidated configurations expire after 48 hours. It is unknown whether anyone exploited the weakness in the wild.

Check
Run npm trust list to confirm each bound repository still belongs to you, rebind any pointing to renamed or transferred repositories, and remove bindings before deleting a repository.
Affected
npm packages bound through Trusted Publishing to a repository or owner that was later renamed, transferred, or deleted could be hijacked by an attacker claiming the freed slug.
Fix
Verify and rebind Trusted Publishing configurations, check that package provenance attestations name the expected repository, and apply the same review to GitLab-based Trusted Publishing.